Hi Tvrtko, I misread your first mail, sorry for that. I did not saw that your device was a Hid one detected as a multitouch one. Under 3.3, just do: $ sudo modprobe hid-multitouch And the device should be handled by hid-multitouch. The 3.3 kernel, detects that your device should be handled by hid-multitouch, but it does not load it automatically. You may add this module in the configuration file. Cheers, Benjamin On Thu, Apr 12, 2012 at 16:47, Tvrtko Ursulin <tvrtko.ursulin@xxxxxxxxxxxx> wrote: > > [Jiri, I copied you as per get_maintainers.pl having trouble debugging > this issue in case linux-input mailing list is dead (can't find recent > archives). My original post plus some debug info is below.] > > On Wednesday 11 Apr 2012 16:29:59 Tvrtko Ursulin wrote: >> Hi all, >> >> I am playing with a multi-touch capable touch screen from the >> above mentioned vendor and are experiencing some problems here. >> On a 3.1.0 derivative kernel it kind of works, looks like this: >> >> [5523460.737596] usb 1-1.6.1.2: new full speed USB device number 18 using >> ehci_hcd [5523460.824952] usb 1-1.6.1.2: New USB device found, >> idVendor=2453, idProduct=0100 [5523460.824959] usb 1-1.6.1.2: New USB >> device strings: Mfr=1, Product=2, SerialNumber=3 [5523460.824964] usb >> 1-1.6.1.2: Product: SDW-190W2-M5T-XXX-XX-PRD >> [5523460.824968] usb 1-1.6.1.2: Manufacturer: Baanto >> [5523460.824971] usb 1-1.6.1.2: SerialNumber: SDW190W2M5T >> [5523460.833233] input: Baanto SDW-190W2-M5T-XXX-XX-PRD as >> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.1/1-1.6.1.2/1-1.6.1.2 >> :1.0/input/input159 [5523460.833926] generic-usb 0003:2453:0100.00A3: >> input,hiddev0,hidraw3: USB HID v1.10 Mouse [Baanto SDW-190W2-M5T- >> XXX-XX-PRD ] on usb-0000:00:1a.0-1.6.1.2/input0 >> >> >> On 3.3.0 it doesn't think it is an input device at all: >> >> [ 73.776660] usb 3-1: new full-speed USB device number 3 using xhci_hcd >> [ 73.817163] usb 3-1: New USB device found, idVendor=2453, idProduct=0100 >> [ 73.817167] usb 3-1: New USB device strings: Mfr=1, Product=2, >> SerialNumber=3 [ 73.817169] usb 3-1: Product: SDW-190W2-M5T-XXX-XX-PRD >> [ 73.817171] usb 3-1: Manufacturer: Baanto >> [ 73.817173] usb 3-1: SerialNumber: SDW190W2M5T >> >> On 3.0 on the other hand it actually registered multiple HID devices, which >> is what I think should happen with this device, because it's datasheet >> says this: >> >> """ >> The mid-size family of touch screens, when enumerated on the OS, expose 5 >> top level USB HID collections. The following table describes these in >> detail: following table describes these in detail: >> >> Collection Description >> ---------------------- >> Win 7 Touch Collection >> Microsoft Device Configuration Collection >> Generic Mouse Collection >> Generic Pointer Collection >> Baanto Touch (Custom HID) Collection >> >> Report Data >> ----------- >> Multi Touch Packets >> Control Packets >> N\A – Future Use >> Single Touch Packet >> Multi Touch Packets\Control Packets >> """ >> >> Any ideas who is at fault here? >> >> Thanks, >> >> Tvrtko >> >> >> Bus 003 Device 003: ID 2453:0100 >> Device Descriptor: >> bLength 18 >> bDescriptorType 1 >> bcdUSB 2.00 >> bDeviceClass 0 (Defined at Interface level) >> bDeviceSubClass 0 >> bDeviceProtocol 0 >> bMaxPacketSize0 64 >> idVendor 0x2453 >> idProduct 0x0100 >> bcdDevice 4.0c >> iManufacturer 1 Baanto >> iProduct 2 SDW-190W2-M5T-XXX-XX-PRD >> iSerial 3 SDW190W2M5T >> bNumConfigurations 1 >> Configuration Descriptor: >> bLength 9 >> bDescriptorType 2 >> wTotalLength 34 >> bNumInterfaces 1 >> bConfigurationValue 1 >> iConfiguration 0 >> bmAttributes 0xc0 >> Self Powered >> MaxPower 500mA >> Interface Descriptor: >> bLength 9 >> bDescriptorType 4 >> bInterfaceNumber 0 >> bAlternateSetting 0 >> bNumEndpoints 1 >> bInterfaceClass 3 Human Interface Device >> bInterfaceSubClass 0 No Subclass >> bInterfaceProtocol 0 None >> iInterface 0 >> HID Device Descriptor: >> bLength 9 >> bDescriptorType 33 >> bcdHID 1.10 >> bCountryCode 33 US >> bNumDescriptors 1 >> bDescriptorType 34 Report >> wDescriptorLength 759 >> Report Descriptors: >> ** UNAVAILABLE ** >> Endpoint Descriptor: >> bLength 7 >> bDescriptorType 5 >> bEndpointAddress 0x81 EP 1 IN >> bmAttributes 3 >> Transfer Type Interrupt >> Synch Type None >> Usage Type Data >> wMaxPacketSize 0x0040 1x 64 bytes >> bInterval 1 >> Device Status: 0x0001 >> Self Powered > > This is all I see with HID debugging turned on (3.3.0) after plugging in the device: > > [85409.156718] drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 0 > [85409.176184] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0123 wIndex=0x0000 wLength=56 > [85409.177652] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0125 wIndex=0x0000 wLength=6 > [85409.179649] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0110 wIndex=0x0000 wLength=6 > [85409.181639] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0109 wIndex=0x0000 wLength=64 > [85409.183636] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x010f wIndex=0x0000 wLength=64 > [85409.185634] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x010b wIndex=0x0000 wLength=64 > [85409.187639] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x010c wIndex=0x0000 wLength=64 > [85409.189633] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x010d wIndex=0x0000 wLength=64 > [85409.191628] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0324 wIndex=0x0000 wLength=2 > [85409.194619] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0327 wIndex=0x0000 wLength=3 > [85409.196621] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0302 wIndex=0x0000 wLength=4 > [85409.199617] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0303 wIndex=0x0000 wLength=13 > [85409.202615] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0304 wIndex=0x0000 wLength=13 > [85409.205606] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0305 wIndex=0x0000 wLength=3 > [85409.208601] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0355 wIndex=0x0000 wLength=2 > [85409.210603] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0377 wIndex=0x0000 wLength=2 > [85409.212604] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0366 wIndex=0x0000 wLength=2 > [85409.214597] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0388 wIndex=0x0000 wLength=2 > [85409.216593] drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0344 wIndex=0x0000 wLength=2 > > No input device of any kind registered after this point. > > Hints about what is going wrong? > > Tvrtko > > -- > 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 -- 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
