Hi Florian, On Fri, Jan 28, 2011 at 17:24, Florian Echtler <floe@xxxxxxxxxxxxxx> wrote: > Hello everyone, > >> The product id is the 42 inches one. I don't know if they have >> other product id for the other size, or if it is a per-size product id. > This is very interesting, I have access to a 65" IrTouch system which > has VID 0x6615 and PID 0x0C20. I wasn't aware that there are already > kernel drivers for their systems, I had been playing around with their > awful binary driver and had done some experiments with libusb. Is there > a documentation of some kind available? We just made the analysis of the hid reports that are send. We have no documentation for this particular device. > >> diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h >> index 92a0d61..b1dd7ad 100644 >> --- a/drivers/hid/hid-ids.h >> +++ b/drivers/hid/hid-ids.h >> @@ -333,6 +333,9 @@ >> #define USB_VENDOR_ID_IMATION 0x0718 >> #define USB_DEVICE_ID_DISC_STAKKA 0xd000 >> >> +#define USB_VENDOR_ID_IRTOUCHSYSTEMS 0x6615 >> +#define USB_DEVICE_ID_IRTOUCH_INFRARED_USB 0x0070 > I will test this on our screen next week. > I assume that I should use the tree from: > http://git.kernel.org/?p=linux/kernel/git/rydberg/input-mt.git;a=summary hid-multitouch is schedulded for 2.6.38. So you can also use the stock 2.6.38-rc2: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary > > Note: after briefly browsing through hid-multitouch.c, it seems to me > that there might be issues; the USB interface on our screen doesn't > report as HID device, but as vendor class (0xFF). This is more problematic. Hardware makers are forced to push hid aware firmware to be win7 certified. Maybe they have a new firmware for your device. Cheers, Benjamin -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
