On Wed, 24 Jan 2007, Radomir Zugic wrote: > Hi Alan, > > thank you for your reply. lsusb -v gives me: > > Bus 001 Device 002: ID 046d:c805 Logitech, Inc. > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 255 Vendor Specific Class > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 16 > idVendor 0x046d Logitech, Inc. > idProduct 0xc805 > bcdDevice 44.24 > iManufacturer 1 Logitech > iProduct 2 Digital Pen > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 55 > bNumInterfaces 2 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xc0 > Self Powered > MaxPower 150mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass 0 > bInterfaceProtocol 255 > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 2 > Transfer Type Bulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0040 1x 64 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0010 1x 16 bytes > bInterval 100 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 0 > bInterfaceClass 254 Application Specific Interface > bInterfaceSubClass 1 Device Firmware Update > bInterfaceProtocol 0 > iInterface 0 > Device Status: 0x0000 > (Bus Powered) > > > Any ideas?
Notice these lines: > bDeviceClass 255 Vendor Specific Class > bInterfaceClass 255 Vendor Specific Class > bInterfaceClass 254 Application Specific Interface They mean what they say. Unless you can get information from the vendor about how the device works, or you can figure it out yourself by reverse-engineering the protocol, you won't be able to drive the device under Linux. If you have USB SnoopyPro data from Windows, you could put it up on a web site and post a message inviting people to look at it. Maybe somebody will recognize the protocol. Alan Stern P.S.: For anyone interested in analyzing SnoopyPro binary output files... Note that as long as you confine yourself to looking at those files and don't try to snoop an actual USB device, SnoopyPro works quite well under Wine. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
