xinput ids

[Peter Korsgaard]

>>>>> "Peter" == Peter Hutterer <peter.hutterer at who-t.net> writes:

Hi,

 >> A typical use case is to set the coordinate transformation matrix for
 >> touchscreens in multihead setups.
 >> 
 >> In the likely situation that the touchscreens are of the same type they
 >> will have the same device name, so you need to fish out the
 >> corresponding /dev/input/event* device node and pass it to udevadm info
 >> (assuming that the server is local) to E.G. key off the ID_PATH
 >> (E.G. the USB port the touchscreen is connected to).

 > yeah, fair enough but that's not what I suspected from the original message
 > (Kai only talks of a single device, afaict).

 > related question for this case though: would xinput get-id call be
 > interesting then? e.g. for two touchscreens you'd get
 > $ xinput get-id "touchscreen"
 > 12 16 

Well, a bit - Bu you'd still need to extract the Device Node property
and pass it to udev, so it doesn't help much.

-- 
Venlig hilsen,
Peter Korsgaard