multi-touch-dev team mailing list archive

[Bryce Harrington <bryce@xxxxxxxxxxxxx>]

On Thu, Apr 08, 2010 at 05:46:20PM -0400, Rafi Rubin wrote:
> On 04/08/10 17:05, Bryce Harrington wrote:
> > On Thu, Apr 08, 2010 at 04:05:09PM -0400, Rafi Rubin wrote:
> >>> P.S.  I've hooked up a Dell MT lcd panel but it seems this is going to
> >>> require a different method for testing
> > 
> > Bus 002 Device 010: ID 1926:0064  
> > 
> > http://accessories.us.dell.com/sna/products/Displays/productdetail.aspx?c=us&l=en&cs=19&sku=320-1172
> 
> Please send the result of "lsusb -vv" and check to see if there's anything in

lsusb -vv : http://pastebin.com/KZ0bFSut

> /debug/hid (mount debugfs if you haven't already).  If there is anything there,

0003:1926:0064.000B : http://pastebin.com/pWmypZ2m
0003:1B96:0001.0007 : http://pastebin.com/39vQVJFT
0003:1B96:0001.0008 : http://pastebin.com/F1VURkK6
0003:413C:8161.0009 : http://pastebin.com/BL5TRBJL
0003:413C:8162.000A : http://pastebin.com/L6zdLUvD

> cat the contents of any "rdesc" files and send those too.  Also "find /dev "
> grep hid", there might be a hidraw or hiddev node sitting around.

/dev/hidraw4
/dev/hidraw3
/dev/hidraw2
/dev/hidraw1
/dev/hidraw0
/dev/usb/hiddev2
/dev/usb/hiddev1
/dev/usb/hiddev0
/dev/.udev/db/hidraw:hidraw4
/dev/.udev/db/usb:hiddev2
/dev/.udev/db/hidraw:hidraw3
/dev/.udev/db/hidraw:hidraw2
/dev/.udev/db/hidraw:hidraw1
/dev/.udev/db/usb:hiddev1
/dev/.udev/db/usb:hiddev0
/dev/.udev/db/hidraw:hidraw0

> I wouldn't be terrible surprised if the device is just masked off and being
> ignored.  If so, the first step is to fix IS_INPUT_APPLICATION in
> include/linux/hid.h.
> 
> If I had to guess I'd say this might be worth a try:
> 
> - - #define IS_INPUT_APPLICATION(a) (((a >= 0x00010000) && (a <= 0x00010008)) ||
> (a == 0x00010080) || (a == 0x000c0001) || ((a >= 0x000d0002) && (a <= 0x000d0006)))
> + #define IS_INPUT_APPLICATION(a) (((a >= 0x00010000) && (a <= 0x00010008)) ||
> (a == 0x00010080) || (a == 0x000c0001) || ((a >= 0x000d0002) && (a <= 0x000d000c)))
> 
> (increase the range from white board to "multiple point digitizer").
> 
> 
> Anyway, at least send the less distracting bits if you have a minute.  You can
> leave your kernel alone if (as if that's in question) you are busy.

Ok, leaving kernel alone for now but I'm up for hacking on it next week
when I will have more time.

Bryce