Quote:
Originally Posted by zxczxc
- - - -
Ideally I would like to be able to simply 'detect' what inputs the usb device is, and read them. But it's easier said than done. Hardcoding it to input2 and input3 was so easy, but as you can see, ugly and doesn't work in all cases.
|
As in examine the /sys tree?
Start with /sys/class/input/* and see if you can find something useful.
I.E:
on my pw-3, version 5.6.1.1 (oldest there is for pw-3) -
input0 is linked to a location with max77696-onkey (the keyboard) in the pathname.
input1 is linked to a location with main_ttsp_core (the touch screen) in the pathname.
I expect the KT(2, 3) to have a different name for the touch screen, since they use the IR scanner of the KT rather than the capacitative touch screen of the others.