HID: add multi-input quirk for NextWindow Touchscreen.
in [Kernel]
|
Prev: : Increase WAIT_DRQ to support slow CF cards
Next: Fix tracing infrastructure to support multiple includes when defining CREATE_TRACE_POINTS
From: Peter Korsgaard on 4 Dec 2009 08:50 >>>>> "Peter" == Peter Hutterer <peter.hutterer(a)redhat.com> writes: Hi, Peter> with the quirk, the device exposes three /dev/input/event files, the Peter> highest of which sends the actual events now (in X/Y). number two Peter> looks like a mouse device (like yours), number three like a Peter> touchscreen (BTN_TOUCH, etc.) Peter> without the quirk, I only get two devices, the second of which looks Peter> like a mix of mouse/touchscreen and it sends ABS_Z/ABS_RX while ABS_X Peter> and ABS_Y are mute. I can get you the full evtest blurb but not before Peter> Monday, the screen is in the office. Ahh ok, strange that I'm not seing the same as you. The reason why there's two devices by default is that the NW pretends to be a keyboard with numlock/scrolllock/caplock so it can go into calibration mode if you press the button a number of times (by default 6). Peter> where do I get nwtool from? google is unusually quiet about it. I guess I need more google-foo ;) It's a tool I wrote: http://git.korsgaard.com/cgi-bin/gitweb.cgi?p=nwtool.git;a=summary You can git clone from http://git.korsgaard.com/git/nwtool.git Nextwindow unfortunately never documented the really interesting commands (like how to make settings persistent), so it cannot do everything the Windows tool can. Peter> is it possible that you changed the report mode (or have it different Peter> to me anyway) and that affects things? Not that I'm aware - I just plugged the device in seconds before running evtest. FYI, now that we're talking about NW touchscreens - How is multiscreen setups with evdev supposed to work? We need something to bind a touchscreen to an Xrandr output to translate (and with 1.3+ reverse transform) the coordinates. In the old days you could use evtouch with seperate X screens and bind the touchscreens to each screen. It's probably offtopic here, but we can move the discussion to the X list if you prefer - Last time I asked there I didn't get any reply though: http://article.gmane.org/gmane.comp.freedesktop.xorg/40071/ -- Bye, Peter Korsgaard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Peter Hutterer on 7 Dec 2009 00:50 On 04/12/09 23:40, Peter Korsgaard wrote: >>>>>> "Peter" == Peter Hutterer<peter.hutterer(a)redhat.com> writes: > Peter> with the quirk, the device exposes three /dev/input/event files, the > Peter> highest of which sends the actual events now (in X/Y). number two > Peter> looks like a mouse device (like yours), number three like a > Peter> touchscreen (BTN_TOUCH, etc.) > Peter> without the quirk, I only get two devices, the second of which looks > Peter> like a mix of mouse/touchscreen and it sends ABS_Z/ABS_RX while ABS_X > Peter> and ABS_Y are mute. I can get you the full evtest blurb but not before > Peter> Monday, the screen is in the office. > > Ahh ok, strange that I'm not seing the same as you. The reason why > there's two devices by default is that the NW pretends to be a keyboard > with numlock/scrolllock/caplock so it can go into calibration mode if > you press the button a number of times (by default 6). evtest output for the mouse device on kernel 2.6.31.6-150.fc12.x86_64, I'll spare you the keyboard device, it's not particularly interesting. Input driver version is 1.0.0 Input device ID: bus 0x3 vendor 0x1926 product 0x3 version 0x100 Input device name: "NextWindow Touchscreen" Supported events: Event type 0 (Sync) Event type 1 (Key) Event code 272 (LeftBtn) Event code 273 (RightBtn) Event code 274 (MiddleBtn) Event code 320 (ToolPen) Event code 330 (Touch) Event type 2 (Relative) Event code 8 (Wheel) Event type 3 (Absolute) Event code 0 (X) Value 16384 Min 0 Max 32767 Event code 1 (Y) Value 16384 Min 0 Max 32767 Event code 2 (Z) Value 15078 Min 0 Max 32767 Event code 3 (Rx) Value 20008 Min 0 Max 32767 Event type 4 (Misc) Event code 4 (ScanCode) Testing ... (interrupt to exit) Event: time 1260143900.146760, type 1 (Key), code 320 (ToolPen), value 1 Event: time 1260143900.146775, type 3 (Absolute), code 2 (Z), value 14953 Event: time 1260143900.146777, type 3 (Absolute), code 3 (Rx), value 19456 Event: time 1260143900.146780, -------------- Report Sync ------------ Event: time 1260143900.150722, type 4 (Misc), code 4 (ScanCode), value d0042 Event: time 1260143900.150729, type 1 (Key), code 330 (Touch), value 1 Event: time 1260143900.150733, -------------- Report Sync ------------ Event: time 1260143900.166736, type 3 (Absolute), code 2 (Z), value 14931 Event: time 1260143900.166750, type 3 (Absolute), code 3 (Rx), value 19440 Event: time 1260143900.166753, -------------- Report Sync ------------ Event: time 1260143900.186736, type 3 (Absolute), code 2 (Z), value 14904 Event: time 1260143900.186749, type 3 (Absolute), code 3 (Rx), value 19394 Event: time 1260143900.186751, -------------- Report Sync ------------ Event: time 1260143900.202737, type 3 (Absolute), code 2 (Z), value 14844 Event: time 1260143900.202751, type 3 (Absolute), code 3 (Rx), value 19223 Event: time 1260143900.202754, -------------- Report Sync ------------ Event: time 1260143900.222737, type 4 (Misc), code 4 (ScanCode), value d0042 Event: time 1260143900.222748, type 1 (Key), code 330 (Touch), value 0 Event: time 1260143900.222753, -------------- Report Sync ------------ Event: time 1260143900.226723, type 1 (Key), code 320 (ToolPen), value 0 > Peter> where do I get nwtool from? google is unusually quiet about it. > > I guess I need more google-foo ;) It's a tool I wrote: > > http://git.korsgaard.com/cgi-bin/gitweb.cgi?p=nwtool.git;a=summary > > You can git clone from http://git.korsgaard.com/git/nwtool.git > > Nextwindow unfortunately never documented the really interesting > commands (like how to make settings persistent), so it cannot do > everything the Windows tool can. > > Peter> is it possible that you changed the report mode (or have it different > Peter> to me anyway) and that affects things? > > Not that I'm aware - I just plugged the device in seconds before running > evtest. [root(a)touchie sbin]# ./nwtool -u -i Version: 2.99 Serial: 617241 Model: 1901 HW capabilities: 0x40 Rightclick delay: 1000 ms Doubleclick time: 200 ms Report mode: 4 Drag threshold: 500 Buzzer time: 40 ms Buzzer tone: 40 Calibration key: 4 Calibration presses: 3 looks like we do have a different reporting mode. Setting mode to 1 with nwtool yields the same information that you provided in your last email. After booting into Vista and resetting the screen to factory defaults, the reporting mode is still 4. > FYI, now that we're talking about NW touchscreens - How is multiscreen > setups with evdev supposed to work? We need something to bind a > touchscreen to an Xrandr output to translate (and with 1.3+ reverse > transform) the coordinates. In the old days you could use evtouch with > seperate X screens and bind the touchscreens to each screen. > > It's probably offtopic here, but we can move the discussion to the X > list if you prefer - Last time I asked there I didn't get any reply > though: > > http://article.gmane.org/gmane.comp.freedesktop.xorg/40071/ Ask louder :) I think I remember your email but it got flooded out of my inbox. In general there should be some method to do that though I need to check the implementation. Cheers, Peter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Peter Korsgaard on 9 Dec 2009 04:50 >>>>> "Peter" == Peter Hutterer <peter.hutterer(a)redhat.com> writes: Hi, Peter> evtest output for the mouse device on kernel Peter> 2.6.31.6-150.fc12.x86_64, I'll spare you the keyboard device, Peter> it's not particularly interesting. Peter> Testing ... (interrupt to exit) Peter> Event: time 1260143900.146760, type 1 (Key), code 320 (ToolPen), value 1 Peter> Event: time 1260143900.146775, type 3 (Absolute), code 2 (Z), value 14953 Peter> Event: time 1260143900.146777, type 3 (Absolute), code 3 (Rx), value 19456 Peter> Event: time 1260143900.146780, -------------- Report Sync ------------ Sorry, it seems like the nw controller I used the other day had old firmware (product 0x1, firmware 2.91). With 2.92 I see the same list of supported events, but I get X/Y events on motion instead of Z / Rx: Event: time 1260344704.138808, type 3 (Absolute), code 0 (X), value 19097 Event: time 1260344704.138814, type 3 (Absolute), code 1 (Y), value 16704 Event: time 1260344704.138819, -------------- Report Sync ------------ Event: time 1260344704.158801, type 3 (Absolute), code 0 (X), value 19033 Event: time 1260344704.158808, type 3 (Absolute), code 1 (Y), value 16700 Event: time 1260344704.158814, -------------- Report Sync ------------ Event: time 1260344704.174803, type 4 (Misc), code 4 (ScanCode), value 90001 Event: time 1260344704.174807, type 1 (Key), code 272 (LeftBtn), value 0 Event: time 1260344704.174825, -------------- Report Sync ------------ Peter> [root(a)touchie sbin]# ./nwtool -u -i Peter> Version: 2.99 Peter> Serial: 617241 Peter> Model: 1901 Peter> HW capabilities: 0x40 Peter> Rightclick delay: 1000 ms Peter> Doubleclick time: 200 ms Peter> Report mode: 4 Peter> Drag threshold: 500 Peter> Buzzer time: 40 ms Peter> Buzzer tone: 40 Peter> Calibration key: 4 Peter> Calibration presses: 3 Hmm, what is report mode 4? Some kind of multi touch mode? What do you see if you install the Nextwindow USB config tool under Windows (unfortunately doesn't work under Wine) and look in the mouse tab? I guess you have a 4th option here. I see this: http://peter.korsgaard.com/nw.png You can get usb config here: http://www.nextwindow.com/nextwindow_support/software.html >> It's probably offtopic here, but we can move the discussion to the X >> list if you prefer - Last time I asked there I didn't get any reply >> though: >> >> http://article.gmane.org/gmane.comp.freedesktop.xorg/40071/ Peter> Ask louder :) I think I remember your email but it got flooded out of Peter> my inbox. In general there should be some method to do that though I Peter> need to check the implementation. OK, great - Let me know what you find. I did hack something up with evtouch, but would like to move to evdev instead. I'm willing to work on getting evdev to handle multi screen touchscreen setups better if needed, I just need a bit of guidance on how it should be handled. -- Bye, Peter Korsgaard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Peter Korsgaard on 17 Dec 2009 15:40 >>>>> "Peter" == Peter Korsgaard <jacmet(a)sunsite.dk> writes: >>> It's probably offtopic here, but we can move the discussion to the X >>> list if you prefer - Last time I asked there I didn't get any reply >>> though: >>> >>> http://article.gmane.org/gmane.comp.freedesktop.xorg/40071/ Peter> Ask louder :) I think I remember your email but it got flooded Peter> out of my inbox. In general there should be some method to do Peter> that though I need to check the implementation. Peter> OK, great - Let me know what you find. I did hack something up Peter> with evtouch, but would like to move to evdev instead. Did you find anything? -- Bye, Peter Korsgaard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Peter Hutterer on 18 Dec 2009 00:10
On 09/12/09 19:42, Peter Korsgaard wrote: > Peter> [root(a)touchie sbin]# ./nwtool -u -i > Peter> Version: 2.99 > Peter> Serial: 617241 > Peter> Model: 1901 > Peter> HW capabilities: 0x40 > Peter> Rightclick delay: 1000 ms > Peter> Doubleclick time: 200 ms > Peter> Report mode: 4 > Peter> Drag threshold: 500 > Peter> Buzzer time: 40 ms > Peter> Buzzer tone: 40 > Peter> Calibration key: 4 > Peter> Calibration presses: 3 > > Hmm, what is report mode 4? Some kind of multi touch mode? > > What do you see if you install the Nextwindow USB config tool under > Windows (unfortunately doesn't work under Wine) and look in the mouse > tab? I guess you have a 4th option here. > > I see this: http://peter.korsgaard.com/nw.png argh. now you made me use vista! ;) Installed version 2.8 today, it offers three modes in his interface: None, HID Mouse and "USB Digitiser". The last one was selected when I started into Vista. There's an extra checkbox "Multi-Touch reporting" that was not ticked. The different combinations and the reporting mode output of nwtool: USB Digitizer - multi-touch not ticked: reporting mode 4 USB Digitizer - multi-touch ticked: reporting mode 3 USB HID Mouse - multi-touch not ticked: reporting mode 1 USB HID Mouse - multi-touch ticked: reporting mode 9 None - multi-touch not ticked: reporting mode 0 None - multi-touch ticked: reporting mode 8 For reporting mode 4 and 3, the events are Z/Rx + touch For reporting mode 1 and 9, the events are ABS_X/Y and left button For reporting mode 0 and 8, no events are sent (unsurprisingly) So it seems the only difference between our two models is the default reporting mode - assuming that 4 is the default, we've had this thing for a year without doing much with it but it could well be that someone set it earlier or one of the HP Touchsmart software pieces changed it. > >> It's probably offtopic here, but we can move the discussion to the X > >> list if you prefer - Last time I asked there I didn't get any reply > >> though: > >> > >> http://article.gmane.org/gmane.comp.freedesktop.xorg/40071/ > > Peter> Ask louder :) I think I remember your email but it got flooded out of > Peter> my inbox. In general there should be some method to do that though I > Peter> need to check the implementation. > > OK, great - Let me know what you find. I did hack something up with > evtouch, but would like to move to evdev instead. > I'm willing to work on getting evdev to handle multi screen touchscreen > setups better if needed, I just need a bit of guidance on how it should > be handled. replying to your email right now. Cheers, Peter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |