On Mon, 9 Dec 2002, Dan Streetman wrote: | | On Mon, 9 Dec 2002, Rui Saraiva wrote: | | >Also, both values are in 0xJJMN format, where JJ is the major version | >number, M is the minor version number and N the sub minor version number. | | what makes you think the format is JJMN? I don't see that anywhere in | the USB spec, at least not that I can find. It would make much more | sense to be a normal BCD instead of some special BCD that uses a | combination of a byte and two nibbles (when all other BCDs | are always nibble-based).
Just MMNN makes more sense to me, but the USB 2.0 spec says in section 9.6.1, page 261: The bcdUSB field contains a BCD version number. The value of the bcdUSB field is 0xJJMN for version JJ.M.N (JJ major version number, M minor version number, N sub-minor version number), e.g., version 2.1.3 is represented with value 0x0213 and version 2.0 is represented with a value of 0x0200. and then table 9-8 goes on to muck it up with: 2 | bcdUSB | 2 | BCD | USB Specification Release Number in Binary-Coded Decimal (i.e., 2.10 is 210H). This field identifies the release of the USB Specification with which the device and its descriptors are compliant. and Table 9-9 mucks it up again: 2 | bcdUSB | 2 | BCD | USB specification version number (e.g., 0200H for V2.00 ) However, the previously-referenced ccs Versioning spec. says, for featureVersion and ccsVersion: 2 | bcdFeatureVersion and bcdCCSVersion | 2 | BCD | A BCD Value that encodes the revision of the CCS Feature as 4 BCD digits where the decimal point is between the 2 nd and 3 rd digits. -- ~Randy ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
