ACTIVE - Linux driver for Thrustmaster wheels https://metanimi.dy.fi/cgit/hid-tmff2/atom?h=master 2026-08-18T18:43:32Z 2026-08-18T18:43:32Z Kimplul kimi.h.kuparinen@gmail.com 2026-08-18T18:43:32Z urn:sha1:461408eef1b3e747f338a902322c6fe517f1db05 + Unnecessary, now that driver itself sets the wanted deadzone. Thanks @kakra! 2026-08-18T18:41:17Z Kimplul kimi.h.kuparinen@gmail.com 2026-08-18T18:26:51Z urn:sha1:456ec7d66d58ee41377022f44618a9b40838f5f9 2026-08-09T20:00:08Z Kimplul kimi.h.kuparinen@gmail.com 2026-08-09T20:00:08Z urn:sha1:c5b9b79d4e61b77e0827e81dd676420b3c366743 fix force feedback arithmetic and wheel input filtering 2026-08-08T22:20:24Z Kai Krakow kai@kaishome.de 2026-08-08T11:04:36Z urn:sha1:4c142e19d14d02d0149198274b0f3f11091c71c6 + HID derives fuzz and flat from the logical axis range. On the tested T300 this gives steering fuzz=255 and flat=4095. It filters small corrections and adds a large centered deadzone before applications apply their own steering model. + Flat is also centered for pedal axes, while their rest position is an endpoint. Fuzz without an endpoint deadzone can retain a small nonzero value after the hardware has returned to rest. Both behaviours are inappropriate for wheel and pedal input, and applications already provide the required steering and endpoint deadzones. + Override fuzz and flat for every available wheel and pedal axis in input_configured on devices handled by hid-tmff2, following the existing hid-universal-pidff precedent for high-resolution racing devices. Skip absent axes through the input device's absbit mask. 2026-08-08T22:20:18Z Kai Krakow kai@kaishome.de 2026-08-08T11:04:25Z urn:sha1:1914c478dec801e98e9b73bbfd5bbdc4c0a11cf8 + Direction scaling can produce 32768 for the valid input pair -32768 and a negative full-scale sine value. Storing the intermediate result in s16 wraps it before constant, ramp or periodic effects are converted. + Keep direction-scaled values in s32 until their destination range is known. Periodic effects cannot represent a magnitude above S16_MAX, so clamp the asymmetric endpoint after making the magnitude positive. This also prevents the following headroom calculation from using a negative wrapped magnitude. 2026-08-08T22:20:08Z Kai Krakow kai@kaishome.de 2026-08-08T10:27:06Z urn:sha1:465ce84d2997e5af6630b88d88b63509d5a88031 + FF_GAIN and the driver gain both use the full 16-bit range. Their product can exceed INT_MAX. Signed overflow is undefined and happens for common settings such as 75 percent times 75 percent. Use a u32 intermediate for the scaling operation. + Pass the configured gain directly when initializing or updating the hardware. This also removes two redundant multiply-divide expressions which could overflow before cancelling out. 2026-08-08T22:20:00Z Kai Krakow kai@kaishome.de 2026-08-08T20:36:04Z urn:sha1:f014217288927246f92ee876afbbf9de8ba707be + Gain is documented and sent to the hardware as a value in the range 0 to 65535, but the module parameter and sysfs attribute accept wider integer values. Store gain as a u16 and parse sysfs writes with kstrtou16 so out-of-range values are rejected instead of being silently changed. + This constrains only the configured value. Calculations combining gain values still require a wider intermediate to cover the product of two full-range 16-bit values. 2026-08-08T13:58:42Z Kimplul kimi.h.kuparinen@gmail.com 2026-08-08T13:58:29Z urn:sha1:9d8577ba2a2c8e3d96cfdb7be4201e4e230e210f + As requested in #153. 2026-03-10T06:18:34Z Kimplul kimi.h.kuparinen@gmail.com 2026-03-10T06:18:34Z urn:sha1:8187920ed261c7024826f8204cc7bea45153a3da 2026-02-08T13:56:57Z Kimplul kimi.h.kuparinen@gmail.com 2026-02-08T13:56:57Z urn:sha1:f004195a73be722f6384ecae7d98161481151dff + Seems appropriate, considering the recent new wheels introduced