The joydev device *is* missing the mappings for the touchpad axes for
some reason (JSIOCGAXES returns 14 instead of 17 like it should). I'm
not sure why though. In the Sony driver the touchpad axis bits are set
in the probe function and work correctly via the evdev interface and
looking in
On 4/22/2014 12:50, si...@mungewell.org wrote:
The joydev device *is* missing the mappings for the touchpad axes for
some reason (JSIOCGAXES returns 14 instead of 17 like it should). I'm
not sure why though. In the Sony driver the touchpad axis bits are set
in the probe function and work
It might be a matter of the joydev module not being loaded into memory
the first time thus allowing the probe function to complete and set the
proper axis bits before the js* device is created. On subsequent
connects the module would already be loaded so the js* device would be
created
Hi,
I've noticed a glitch with the Dualshock4 on 3.15rc1 (plus LEDs patch, if
that makes a difference).
Sometimes everything works as expected, the thumbsticks work OK and the
touch-pad changes axis 15 16 (as reported by jstest). Other times axis
15 and 16 do not report changes, instead axis 0
Hi,
I've noticed a glitch with the Dualshock4 on 3.15rc1 (plus LEDs patch, if
that makes a difference).
Seems only to work on the the first time the device is connected (with
USB), even in 'repair' mode (with no GUI). Subsequent plug-ins shows axis
0 being corrupted.
Checking through the
On 4/21/2014 12:49, si...@mungewell.org wrote:
Hi,
I've noticed a glitch with the Dualshock4 on 3.15rc1 (plus LEDs patch, if
that makes a difference).
Sometimes everything works as expected, the thumbsticks work OK and the
touch-pad changes axis 15 16 (as reported by jstest). Other times axis
On 4/21/2014 13:30, Frank Praznik wrote:
On 4/21/2014 12:49, si...@mungewell.org wrote:
Hi,
I've noticed a glitch with the Dualshock4 on 3.15rc1 (plus LEDs
patch, if
that makes a difference).
Sometimes everything works as expected, the thumbsticks work OK and the
touch-pad changes axis 15
