atom feed19 messages in org.freebsd.freebsd-hackersTricky USB device.
FromSent OnAttachments
David GilbertApr 8, 2005 9:40 am 
Maksim YevmenkinApr 8, 2005 9:48 am 
David GilbertApr 8, 2005 9:56 am 
Maksim YevmenkinApr 8, 2005 10:10 am 
David GilbertApr 8, 2005 10:16 am 
Bernd WalterApr 8, 2005 12:05 pm 
David GilbertApr 8, 2005 3:12 pm 
Maksim YevmenkinApr 8, 2005 3:33 pm 
Bernd WalterApr 8, 2005 4:12 pm 
Bernd WalterApr 8, 2005 4:33 pm 
Maksim YevmenkinApr 8, 2005 4:47 pm 
Bernd WalterApr 8, 2005 5:31 pm 
Julian ElischerApr 8, 2005 6:06 pm 
Bernd WalterApr 8, 2005 9:02 pm 
David GilbertApr 9, 2005 2:05 pm 
Bernd WalterApr 9, 2005 2:24 pm 
David GilbertApr 9, 2005 2:48 pm 
Bernd WalterApr 9, 2005 2:57 pm 
David GilbertApr 9, 2005 7:39 pm 
Subject:Tricky USB device.
From:David Gilbert (dgil@dclg.ca)
Date:Apr 8, 2005 9:56:04 am
List:org.freebsd.freebsd-hackers

"Maksim" == Maksim Yevmenkin <maks@savvis.net> writes:

... I don't know if this is hindering me. The usbhid* commands aren't particularly helpful. The port udesc_dump seems only to work on ugen devices ... and ugen doesn't pop up for this device.

Maksim> how about getting usb hid descriptor, parsing and dumping it? Maksim> check out libusbhid - man usbhid(3). it might be that all you Maksim> need to do is to create hid report and send it to the Maksim> device. libusbhid(3) will help you with that.

Tried that. The usb_get_report_desc() returns NULL. This is not a complicated device --- it's not even technically a "human interface" device.

I suppose I need to know how to supress uhid ... or to make ugen show up. It would also be nice to know how to generically poke the interupt enpoints...

Maksim> well comment out 'device uhid' from your kernel config and Maksim> rebuilding the kernel should do the trick.

I wanted to try to avoid that since I use many USB devices, but it's a last resort kind-of-thing.

The documentation for the device describes the interface as simply using the two interupt endpoints (read and write).

Dave.