[<<][usb][>>][..]
Fri Apr 8 14:35:32 EDT 2011
USB low-level
Following _usb.f : making sense of the different request dispatch
levels. Each level is one decision down the tree, following only the
first ones.
level 0: dispatch UIR interrupts: error, soframe, idle, activity,
stall, reset and transaction.
level 1: transaction:
- IN
- OUT
- SETUP
level 2: SETUP
- 0 GET_STATUS
- 1 CLEAR_STATUS
- 3 SET_FEATURE
- 5 SET_ADDRESS
- 6 GET_DESCRIPTOR
- 7 SET_DESCRIPTOR
- 8 GET_CONFIGURATION
- 9 SET_CONFIGURATION
- A GET_INTERFACE
- B SET_INTERFACE
level 3: GET_DESCRIPTOR
- 1 DEVICE
- 2 CONFIGURATION
- 3 STRING
- 4 INTERFACE
- 5 ENDPOINT
What about this:
- generate macros for all code that simply returns a fixed reply
packet.
- use long names:
SETUP.GET_DESCRIPTOR.DEVICE
[Reply][About]
[<<][usb][>>][..]