Le mardi 22 août 2017, Frédéric a écrit :
> Je viens de tenter libinput, comme pour le vlacier, mais ça chie :
jblah mleuh nurfl... vlacier -> clavier !
Bon, la sortie de :
$ xinput list-props
me dit :
Device 'Elo Serial TouchScreen':
Device Enabled (117): 1
Coordinate Transformation Matrix (119): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Calibration Matrix (475): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Calibration Matrix Default (476): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Send Events Modes Available (240): 1, 0
libinput Send Events Mode Enabled (241): 0, 0
libinput Send Events Mode Enabled Default (242): 0, 0
Device Node (243): "/dev/input/event12"
Device Product ID (244): 41, 0
Du coup, j'ai ajouté à la config xorg.conf :
Option "Device" "/dev/input/event12"
et là, j'ai maintenant :
[ 4814.048] (II) config/udev: Adding input device Elo Serial TouchScreen (/dev/input/event12)
[ 4814.048] (**) Elo Serial TouchScreen: Applying InputClass "libinput touchscreen catchall"
[ 4814.048] (**) Elo Serial TouchScreen: Applying InputClass "calibration"
[ 4814.048] (II) Using input driver 'libinput' for 'Elo Serial TouchScreen'
[ 4814.048] (**) Elo Serial TouchScreen: always reports core events
[ 4814.048] (**) Option "Device" "/dev/input/event12"
[ 4814.048] (**) Option "_source" "server/udev"
[ 4814.049] (II) event12 - (II) Elo Serial TouchScreen: (II) is tagged by udev as: Touchscreen
[ 4814.050] (II) event12 - (II) Elo Serial TouchScreen: (II) device is a touch device
[ 4814.050] (II) event12 - (II) Elo Serial TouchScreen: (II) device removed
[ 4814.096] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.1/usb3/3-1/3-1:1.0/ttyUSB0/tty/ttyUSB0/serio2/input/input15/event12"
[ 4814.096] (II) XINPUT: Adding extended input device "Elo Serial TouchScreen" (type: TOUCHSCREEN, id 10)
[ 4814.096] (**) Option "AccelerationScheme" "none"
[ 4814.096] (**) Elo Serial TouchScreen: (accel) selected scheme none/0
[ 4814.096] (**) Elo Serial TouchScreen: (accel) acceleration factor: 2.000
[ 4814.096] (**) Elo Serial TouchScreen: (accel) acceleration threshold: 4
[ 4814.098] (II) event12 - (II) Elo Serial TouchScreen: (II) is tagged by udev as: Touchscreen
[ 4814.098] (II) event12 - (II) Elo Serial TouchScreen: (II) device is a touch device
[ 4814.099] (II) config/udev: Adding input device Elo Serial TouchScreen (/dev/input/mouse1)
[ 4814.099] (**) Elo Serial TouchScreen: Applying InputClass "calibration"
[ 4814.099] (II) Using input driver 'libinput' for 'Elo Serial TouchScreen'
[ 4814.100] (**) Elo Serial TouchScreen: always reports core events
[ 4814.100] (**) Option "Device" "/dev/input/event12"
[ 4814.100] (**) Option "_source" "server/udev"
[ 4814.101] (II) event12 - (II) Elo Serial TouchScreen: (II) is tagged by udev as: Touchscreen
[ 4814.101] (II) event12 - (II) Elo Serial TouchScreen: (II) device is a touch device
[ 4814.101] (II) event12 - (II) Elo Serial TouchScreen: (II) device removed
[ 4814.120] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:13.1/usb3/3-1/3-1:1.0/ttyUSB0/tty/ttyUSB0/serio2/input/input15/mouse1"
[ 4814.120] (II) XINPUT: Adding extended input device "Elo Serial TouchScreen" (type: TOUCHSCREEN, id 11)
[ 4814.120] (**) Option "AccelerationScheme" "none"
[ 4814.120] (**) Elo Serial TouchScreen: (accel) selected scheme none/0
[ 4814.120] (**) Elo Serial TouchScreen: (accel) acceleration factor: 2.000
[ 4814.120] (**) Elo Serial TouchScreen: (accel) acceleration threshold: 4
[ 4814.121] (II) event12 - (II) Elo Serial TouchScreen: (II) is tagged by udev as: Touchscreen
[ 4814.121] (II) event12 - (II) Elo Serial TouchScreen: (II) device is a touch device
Ça paraît mieux, mais ça n'a rien changé côté pointeur :o/ X est toujours
inversé, et la calibration n'a pas été prise en compte. Je pense que les
paramètres ne sont pas bon ; il faudrait modifier les matrices de
transformation et de coordonnées :
https://wiki.ubuntu.com/X/InputCoordinateTransformation
Mais bon, à la mano, c'est un peu merdique. Y'a pas d'autres outils
capables de générer ces matrices, en pointant des cibles ?
--
Frédéric