Writing linux usb device drivers is not a difficult task as the usb-skeleton driver shows. this driver, combined with the other current usb drivers, should provide enough examples to help a beginning author create a working driver in a minimal amount of time.. A device descriptor describes general information about a usb device. it includes information that applies globally to the device and all of the device’s configurations.. The first goal in trying to write a driver for a device is to determine how to control the device. delcom engineering is nice enough to ship the entire usb protocol specification their devices use with the product, and it also is available on-line for free..
Here’s another “hairball” post about usb devices and drivers on linux. i wish some expert would write the definitive “here’s how to reverse-engineer a usb device and write a new usb driver” guide.. Device 003: this is the third device attached to bus 002, the other two devices are “linux foundation 2.0 root hub” and ” intel corp. integrated rate matching hub” id 0781:5567 is the number given to this sandisk, the number before : indicates the manufacture id and number after : indicates device id.. Video devices and usb-to-serial devices are a good example where there is no defined standard, and a driver is devices consist of configurations, interfaces, and endpoints and how usb drivers bind to usb interfaces, not the entire usb device. the speaker example, linux needs two different drivers for one hardware device..