HID: add multi-input quirk for NextWindow Touchscreen.
PATCH 1/1 HID: add multi-input quirk for NextWindow Touchscreen.
These touchscreens are mounted onto HP TouchSmart and the Dell Studio One
19. Without a quirk they report a wrong button set and the x/y coordinates through ABS_Z/ABS_RX, confusing the higher levels (most notably X.Org's evdev driver).
Device id 0x003 covers models 1900, 2150, and 2700 [1] though testing could only be performed on a model 1900.
[1] http://www.nextwindow.com/nextwindow_support/latest_tech_info.html
--- drivers/hid/hid-ids.h | 3 +++ drivers/hid/usbhid/hid-quirks.c | 1 + 2 files changed, 4 insertions(+), 0 deletions(-)
drivers/hid/hid-ids.h +3 -0
@@ -346,6 +346,9 @@#define USB_VENDOR_ID_NEC 0x073e#define USB_DEVICE_ID_NEC_USB_GAME_PAD 0x0301 +#define USB_VENDOR_ID_NEXTWINDOW 0x1926 +#define USB_DEVICE_ID_NEXTWINDOW_TOUCHSCREEN 0x0003 +#define USB_VENDOR_ID_NTRIG 0x1b96#define USB_DEVICE_ID_NTRIG_TOUCH_SCREEN 0x0001
drivers/hid/usbhid/hid-quirks.c +1 -0
@@ -37,6 +37,7 @@ static const struct hid_blacklist { { USB_VENDOR_ID_HAPP, USB_DEVICE_ID_UGCI_FIGHTING, HID_QUIRK_BADPAD | HID_QUIRK_MULTI_INPUT }, { USB_VENDOR_ID_NATSU, USB_DEVICE_ID_NATSU_GAMEPAD, HID_QUIRK_BADPAD }, { USB_VENDOR_ID_NEC, USB_DEVICE_ID_NEC_USB_GAME_PAD, HID_QUIRK_BADPAD }, + { USB_VENDOR_ID_NEXTWINDOW, USB_DEVICE_ID_NEXTWINDOW_TOUCHSCREEN, HID_QUIRK_MULTI_INPUT}, { USB_VENDOR_ID_SAITEK, USB_DEVICE_ID_SAITEK_RUMBLEPAD, HID_QUIRK_BADPAD }, { USB_VENDOR_ID_TOPMAX, USB_DEVICE_ID_TOPMAX_COBRAPAD, HID_QUIRK_BADPAD },
Signature · 6 lines
1.6.5.2 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Jiri Kosina
AppliedQuoted 8 lines · Peter Hutterer
These touchscreens are mounted onto HP TouchSmart and the Dell Studio One
19. Without a quirk they report a wrong button set and the x/y coordinates through ABS_Z/ABS_RX, confusing the higher levels (most notably X.Org's evdev driver).Device id
0x003covers models 1900, 2150, and 2700 [1] though testing could only be performed on a model 1900.
Quoted 7 lines
[1] http://www.nextwindow.com/nextwindow_support/latest_tech_info.html
Signed-off-by Peter Hutterer <[email protected]>--- drivers/hid/hid-ids.h | 3 +++ drivers/hid/usbhid/hid-quirks.c | 1 + 2 files changed, 4 insertions(+), 0 deletions(-)
Applied, thanks Peter.
Signature · 2 lines
Jiri Kosina SUSE Labs, Novell Inc.
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Hutterer <[email protected]> writes:
Peter> These touchscreens are mounted onto HP TouchSmart and the Dell Peter> Studio One 19. Without a quirk they report a wrong button set Peter> and the x/y coordinates through ABS_Z/ABS_RX, confusing the Peter> higher levels (most notably X.Org's evdev driver).
What exactly does this fix? I've been using NW touchscreens for a while and don't recall any issues (admittedly only used it with evtouch).
Signature · 1 line
Bye, Peter Korsgaard
Quoted 9 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Hutterer<[email protected]> writes:
Peter> These touchscreens are mounted onto HP TouchSmart and the Dell Peter> Studio One 19. Without a quirk they report a wrong button set Peter> and the x/y coordinates through ABS_Z/ABS_RX, confusing the Peter> higher levels (most notably X.Org's evdev driver).What exactly does this fix? I've been using NW touchscreens for a while and don't recall any issues (admittedly only used it with evtouch).
evtouch has the following code:
if ( (ev->code == ABS_X) || (ev->code == ABS_Z) ) {
priv->raw_x = ev->value;
pos_changed = 1;
}
if ( (ev->code == ABS_Y) || (ev->code == ABS_RX) ) {
priv->raw_y = ev->value;
pos_changed = 1;
}it's a hack in userspace that works around wrong event reporting. So yes, it works if you're using evtouch but if you want to use any other driver that driver needs the same hack. treating Z as X and RX as Y doesn't work too well for a generic driver such as evdev, which has to deal with devices where RX is a valid axis.
Cheers,
Peter
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Hutterer <[email protected]> writes:
Hi,
Peter> it's a hack in userspace that works around wrong event Peter> reporting. So yes, it works if you're using evtouch but if you Peter> want to use any other driver that driver needs the same Peter> hack. treating Z as X and RX as Y doesn't work too well for a Peter> generic driver such as evdev, which has to deal with devices Peter> where RX is a valid axis.
Hmm, I don't see it sending Z / RX:
sudo evtest /dev/input/event12
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x1926 product 0x1 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 type 3 (Absolute)
Event code 0 (X)
Value 0
Min 0
Max 32767
Event code 1 (Y)
Value 0
Min 0
Max 32767
Event type 4 (Misc)
Event code 4 (ScanCode)
Testing ... (interrupt to exit)
sudo nwtool -u -i
Version: 2.91 Serial: 233025 Model: 1900 HW capabilities: 0x40 Rightclick delay: 1000 ms Doubleclick time: 200 ms Report mode: 1 Drag threshold: 500 Buzzer time: 40 ms Buzzer tone: 40 Calibration key: 4 Calibration presses: 3
Signature · 1 line
Bye, Peter Korsgaard
Quoted 24 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Hutterer<[email protected]> writes:
Peter> it's a hack in userspace that works around wrong event Peter> reporting. So yes, it works if you're using evtouch but if you Peter> want to use any other driver that driver needs the same Peter> hack. treating Z as X and RX as Y doesn't work too well for a Peter> generic driver such as evdev, which has to deal with devices Peter> where RX is a valid axis.Hmm, I don't see it sending Z / RX:
sudo evtest
/dev/input/event12
Input driver version is 1.0.0
Input device ID: bus0x3vendor0x1926product0x1version0x100Input 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 type 3 (Absolute)
Event code 0 (X)
Value 0
Min 0
Quoted 8 lines
Max 32767
Event code 1 (Y)
Value 0
Min 0
Max 32767
Event type 4 (Misc)
Event code 4 (ScanCode)
Testing ... (interrupt to exit)
with the quirk, the device exposes three /dev/input/event files, the highest of which sends the actual events now (in X/Y). number two looks like a mouse device (like yours), number three like a touchscreen (BTN_TOUCH, etc.) without the quirk, I only get two devices, the second of which looks like a mix of mouse/touchscreen and it sends ABS_Z/ABS_RX while ABS_X and ABS_Y are mute. I can get you the full evtest blurb but not before Monday, the screen is in the office.
Quoted 13 lines
sudo nwtool -u -i
Version: 2.91 Serial: 233025 Model: 1900 HW capabilities: 0x40 Rightclick delay: 1000 ms Doubleclick time: 200 ms Report mode: 1 Drag threshold: 500 Buzzer time: 40 ms Buzzer tone: 40 Calibration key: 4 Calibration presses: 3
where do I get nwtool from? google is unusually quiet about it.
is it possible that you changed the report mode (or have it different to me anyway) and that affects things?
Cheers,
Peter
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Hutterer <[email protected]> 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/
Signature · 5 lines
Bye, Peter Korsgaard -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 10 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Hutterer<[email protected]> 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.
Quoted 4 lines
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
Quoted 12 lines
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.
Quoted 5 lines
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@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.
Quoted 11 lines
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:
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
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Hutterer <[email protected]> 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@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
Quoted 5 lines
Quoted 5 lines
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:
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.
Signature · 5 lines
Bye, Peter Korsgaard -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
Quoted 1 line
"Peter" == Peter Korsgaard <[email protected]> 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:
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?
Signature · 1 line
Bye, Peter Korsgaard
Quoted 14 lines · Peter Korsgaard
Peter> [root@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
Quoted 7 lines
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.
Quoted 10 lines
Quoted 5 lines
Quoted 5 lines
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:
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.
Quoted 5 lines
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
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Hutterer <[email protected]> writes:
Hi,
Quoted 1 line
Quoted 1 line
I see this: http://peter.korsgaard.com/nw.png
Peter> argh. now you made me use vista! ;)
Sorry, I promise it won't happen again ;)
Peter> For reporting mode 4 and 3, the events are Z/Rx + touch Peter> For reporting mode 1 and 9, the events are ABS_X/Y and left button Peter> For reporting mode 0 and 8, no events are sent (unsurprisingly)
Peter> So it seems the only difference between our two models is the default Peter> reporting mode - assuming that 4 is the default, we've had this thing Peter> for a year without doing much with it but it could well be that Peter> someone set it earlier or one of the HP Touchsmart software pieces Peter> changed it.
Ok, thanks for checking it all out! Just to be completely sure, the quirk doesn't cause any problems in mode 1/9, right?
Quoted 3 lines
Quoted 3 lines
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.
Peter> replying to your email right now.
Thanks.
Signature · 5 lines
Bye, Peter Korsgaard -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 14 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Hutterer<[email protected]> writes:
Hi,
Quoted 1 line
Quoted 1 line
I see this: http://peter.korsgaard.com/nw.png
Peter> argh. now you made me use vista! ;)
Sorry, I promise it won't happen again ;)
Peter> For reporting mode 4 and 3, the events are Z/Rx + touch Peter> For reporting mode 1 and 9, the events are ABS_X/Y and left button Peter> For reporting mode 0 and 8, no events are sent (unsurprisingly)
Quoted 8 lines
Peter> So it seems the only difference between our two models is the default Peter> reporting mode - assuming that 4 is the default, we've had this thing Peter> for a year without doing much with it but it could well be that Peter> someone set it earlier or one of the HP Touchsmart software pieces Peter> changed it.Ok, thanks for checking it all out! Just to be completely sure, the quirk doesn't cause any problems in mode 1/9, right?
no, the evtest output looks the same with and without the quirk, including right button emulation on long press, etc.
Cheers,
Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Peter" == Peter Hutterer <[email protected]> writes:
Hi,
Quoted 2 lines
Quoted 2 lines
Ok, thanks for checking it all out! Just to be completely sure, the quirk doesn't cause any problems in mode 1/9, right?
Peter> no, the evtest output looks the same with and without the quirk, Peter> including right button emulation on long press, etc.
Perfect, thanks!
Signature · 1 line
Bye, Peter Korsgaard