[libhid-discuss] Find the path...

Matthias Lohr malo at dasevil.de
Fri Dec 7 16:58:33 UTC 2007


Ok, none of the { 0xffa000a5, 0xffa000a6 } etc variants works... so... is this 
the complete path? 

On Thursday 06 December 2007 22:25:46 Charles Lepple wrote:
> Matthias Lohr wrote:
> > 2.6.20-16-generic.
> >
> > It's not possible to figure out the path with this data?
> >
> > parse tree of HIDInterface 002/019[0]:
> > path: 0xffa000a5.0xffa000a6; type: 0x80
>
> { 0xffa000a5, 0xffa000a6 }
>
> > path: 0xffa000a5.0xffa000a7; type: 0x80
>
> { 0xffa000a5, 0xffa000a7 }
>
> > path: 0xffa000a5.0x00000000; type: 0x80
>
> This is left-over from the last path.
>
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0x00000000; type: 0x80
> > path: 0xffa000a5.0xffa000a9; type: 0x90
>
> Similarly, I think this is the input path. (You'll have to check the code
> to see how the types map - I don't have the source in front of me at the
> moment.)
>
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> > path: 0xffa000a5.0x00000000; type: 0x90
> >
> > Greetings
> > Matthias Lohr
> >
> > On Thursday 06 December 2007 21:00:23 Charles Lepple wrote:
> >> Strange. What kernel version are you using?
> >>
> >> Matthias Lohr wrote:
> >> > matthias at scripterhome:~$ sudo libhid-detach-device 04b4:0f1f
> >> > Trying to detach HID with IDs 04b4:0f1f... done.
> >> > matthias at scripterhome:~$ sudo lsusb -d 04b4:0f1f -vvv
> >> > matthias at scripterhome:~$ sudo lsusb -d 04b4:0f1f -vvv
> >> >
> >> > Bus 001 Device 005: ID 04b4:0f1f Cypress Semiconductor Corp.
> >> > Device Descriptor:
> >> >   bLength                18
> >> >   bDescriptorType         1
> >> >   bcdUSB               1.10
> >> >   bDeviceClass            0 (Defined at Interface level)
> >> >   bDeviceSubClass         0
> >> >   bDeviceProtocol         0
> >> >   bMaxPacketSize0         8
> >> >   idVendor           0x04b4 Cypress Semiconductor Corp.
> >> >   idProduct          0x0f1f
> >> >   bcdDevice            1.10
> >> >   iManufacturer           1 Digital Enlightenment
> >> >   iProduct                2 Sunlight Killer
> >> >   iSerial                 3 0000000000000532
> >> >   bNumConfigurations      1
> >> >   Configuration Descriptor:
> >> >     bLength                 9
> >> >     bDescriptorType         2
> >> >     wTotalLength           41
> >> >     bNumInterfaces          1
> >> >     bConfigurationValue     1
> >> >     iConfiguration          0
> >> >     bmAttributes         0x80
> >> >       (Bus Powered)
> >> >     MaxPower              200mA
> >> >     Interface Descriptor:
> >> >       bLength                 9
> >> >       bDescriptorType         4
> >> >       bInterfaceNumber        0
> >> >       bAlternateSetting       0
> >> >       bNumEndpoints           2
> >> >       bInterfaceClass         3 Human Interface Devices
> >> >       bInterfaceSubClass      0 No Subclass
> >> >       bInterfaceProtocol      0 None
> >> >       iInterface              0
> >> >         HID Device Descriptor:
> >> >           bLength                 9
> >> >           bDescriptorType        33
> >> >           bcdHID               1.10
> >> >           bCountryCode            0 Not supported
> >> >           bNumDescriptors         1
> >> >           bDescriptorType        34 Report
> >> >           wDescriptorLength      36
> >> >          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     0x0021  1x 33 bytes
> >> >         bInterval               1
> >> >       Endpoint Descriptor:
> >> >         bLength                 7
> >> >         bDescriptorType         5
> >> >         bEndpointAddress     0x02  EP 2 OUT
> >> >         bmAttributes            3
> >> >           Transfer Type            Interrupt
> >> >           Synch Type               None
> >> >           Usage Type               Data
> >> >         wMaxPacketSize     0x0021  1x 33 bytes
> >> >         bInterval               1
> >> > Device Status:     0x0000
> >> >   (Bus Powered)
> >> > matthias at scripterhome:~$
> >> >
> >> > Look at the beginning. I have to exec lsusb two times, before i get
> >>
> >> some
> >>
> >> > output! after the first lsusb, the usbhid driver is loaded for this
> >> > device!
> >> >
> >> > Greetings
> >> > Matthias Lohr
> >> >
> >> > On Wednesday 05 December 2007 14:39:59 Charles Lepple wrote:
> >> >> That doesn't sound right. If you re-plug the device, the kernel
> >> >> usbhid driver will claim it again, but running test_libhid (or
> >>
> >> libhid-
> >>
> >> >> detach-device, also included in libhid) should make lsusb show the
> >> >> descriptor.
> >> >>
> >> >> Are there any errors in dmesg?
> >> >>
> >> >> Do you have read+write permissions to the device node (in /proc/bus/
> >> >> usb or /dev/bus/usb)?
> >> >>
> >> >> What does "cat /proc/bus/usb/devices" say?
> >> >>
> >> >> On Dec 5, 2007, at 1:28 AM, Matthias Lohr wrote:
> >> >> > Doesn't work. lsusb seems to reload the usb driver...
> >> >> >
> >> >> > Matthias
> >> >> >
> >> >> > On Wednesday 05 December 2007 01:44:57 Charles Lepple wrote:
> >> >> >> On Dec 4, 2007, at 7:28 PM, Peter Stuge wrote:
> >> >> >>> On Tue, Dec 04, 2007 at 08:47:11PM +0100, Matthias Lohr wrote:
> >> >> >>>> // lsusb
> >> >> >>>>     Report Descriptors:
> >> >> >>>>       ** UNAVAILABLE **
> >> >> >>>
> >> >> >>> Disable the HID driver to make it available.
> >> >> >>>
> >> >> >>> Either unload the driver or write a small program to call
> >> >> >>> usb_detach_driver_np() in libusb, or the equivalent in libhid.
> >> >> >>
> >> >> >> Matthias,
> >> >> >>
> >> >> >> Peter is right, but by running the test program, you detached the
> >> >> >> driver. Try running lsusb again.
> >> >> >
> >> >> > _______________________________________________
> >> >> > libhid-discuss mailing list
> >> >> > libhid-discuss at lists.alioth.debian.org
> >> >> > http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
> >> >>
> >> >> _______________________________________________
> >> >> libhid-discuss mailing list
> >> >> libhid-discuss at lists.alioth.debian.org
> >> >> http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
> >> >
> >> > _______________________________________________
> >> > libhid-discuss mailing list
> >> > libhid-discuss at lists.alioth.debian.org
> >> > http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
> >
> > _______________________________________________
> > libhid-discuss mailing list
> > libhid-discuss at lists.alioth.debian.org
> > http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss




More information about the libhid-discuss mailing list