John Chen wrote:
> Tom,
> Would you please show me how did you get bmRequestType to value 0xC2.
I did this so often that I finally created a "cheat sheet" that I keep
in a text file.
+---+---+---+---+---+---+---+---+
| d | type | | recip |
+---+---+---+---+---+---+---+---+
| | |
| +- 0 Standard +- 0 Device
| 1 Class 1 Interface
| 2 Vendor 2 Endpoint
| 3 Other
+- 0 To device
1 From device
00 Standard device, outgoing
01 Standard interface, outgoing
02 Standard endpoint, outgoing
03 Standard other, outgoing
20 Class device, outgoing
21 Class interface, outgoing
22 Class endpoint, outgoing
23 Class other, outgoing
40 Vendor device, outgoing
41 Vendor interface, outgoing
42 Vendor endpoint, outgoing
43 Vendor other, outgoing
80 Standard device, incoming
81 Standard interface, incoming
82 Standard endpoint, incoming
83 Standard other, incoming
a0 Class device, incoming
a1 Class interface, incoming
a2 Class endpoint, incoming
a3 Class other, incoming
c0 Vendor device, incoming
c1 Vendor interface, incoming
c2 Vendor endpoint, incoming
c3 Vendor other, incoming
All other values of bmRequestType are invalid.
--
Tim Roberts, [email protected]
Providenza & Boekelheide, Inc.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
libusbx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
