Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.

USB-ID-FAQ.txt 6.9KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149
  1. Version 2009-08-22
  2. ==========================
  3. WHY DO WE NEED THESE IDs?
  4. ==========================
  5. USB is more than a low level protocol for data transport. It also defines a
  6. common set of requests which must be understood by all devices. And as part
  7. of these common requests, the specification defines data structures, the
  8. USB Descriptors, which are used to describe the properties of the device.
  9. From the perspective of an operating system, it is therefore possible to find
  10. out basic properties of a device (such as e.g. the manufacturer and the name
  11. of the device) without a device-specific driver. This is essential because
  12. the operating system can choose a driver to load based on this information
  13. (Plug-And-Play).
  14. Among the most important properties in the Device Descriptor are the USB
  15. Vendor- and Product-ID. Both are 16 bit integers. The most simple form of
  16. driver matching is based on these IDs. The driver announces the Vendor- and
  17. Product-IDs of the devices it can handle and the operating system loads the
  18. appropriate driver when the device is connected.
  19. It is obvious that this technique only works if the pair Vendor- plus
  20. Product-ID is unique: Only devices which require the same driver can have the
  21. same pair of IDs.
  22. =====================================================
  23. HOW DOES THE USB STANDARD ENSURE THAT IDs ARE UNIQUE?
  24. =====================================================
  25. Since it is so important that USB IDs are unique, the USB Implementers Forum,
  26. Inc. (usb.org) needs a way to enforce this legally. It is not forbidden by
  27. law to build a device and assign it any random numbers as IDs. Usb.org
  28. therefore needs an agreement to regulate the use of USB IDs. The agreement
  29. binds only parties who agreed to it, of course. Everybody else is free to use
  30. any numbers for their IDs.
  31. So how can usb.org ensure that every manufacturer of USB devices enters into
  32. an agreement with them? They do it via trademark licensing. Usb.org has
  33. registered the trademark "USB", all associated logos and related terms. If
  34. you want to put an USB logo on your product or claim that it is USB
  35. compliant, you must license these trademarks from usb.org. And this is where
  36. you enter into an agreement. See the "USB-IF Trademark License Agreement and
  37. Usage Guidelines for the USB-IF Logo" at
  38. http://www.usb.org/developers/logo_license/.
  39. Licensing the USB trademarks requires that you buy a USB Vendor-ID from
  40. usb.org (one-time fee of ca. 2,000 USD), that you become a member of usb.org
  41. (yearly fee of ca. 4,000 USD) and that you meet all the technical
  42. specifications from the USB spec.
  43. This means that most hobbyists and small companies will never be able to
  44. become USB compliant, just because membership is so expensive. And you can't
  45. be compliant with a driver based on V-USB anyway, because the AVR's port pins
  46. don't meet the electrical specifications for USB. So, in principle, all
  47. hobbyists and small companies are free to choose any random numbers for their
  48. IDs. They have nothing to lose...
  49. There is one exception worth noting, though: If you use a sub-component which
  50. implements USB, the vendor of the sub-components may guarantee USB
  51. compliance. This might apply to some or all of FTDI's solutions.
  52. =======================================================================
  53. WHY SHOULD YOU OBTAIN USB IDs EVEN IF YOU DON'T LICENSE USB TRADEMARKS?
  54. =======================================================================
  55. You have learned in the previous section that you are free to choose any
  56. numbers for your IDs anyway. So why not do exactly this? There is still the
  57. technical issue. If you choose IDs which are already in use by somebody else,
  58. operating systems will load the wrong drivers and your device won't work.
  59. Even if you choose IDs which are not currently in use, they may be in use in
  60. the next version of the operating system or even after an automatic update.
  61. So what you need is a pair of Vendor- and Product-IDs for which you have the
  62. guarantee that no USB compliant product uses them. This implies that no
  63. operating system will ever ship with drivers responsible for these IDs.
  64. ==============================================
  65. HOW DOES OBJECTIVE DEVELOPMENT HANDLE USB IDs?
  66. ==============================================
  67. Objective Development gives away pairs of USB-IDs with their V-USB licenses.
  68. In order to ensure that these IDs are unique, Objective Development has an
  69. agreement with the company/person who has bought the USB Vendor-ID from
  70. usb.org. This agreement ensures that a range of USB Product-IDs is reserved
  71. for assignment by Objective Development and that the owner of the Vendor-ID
  72. won't give it to anybody else.
  73. This means that you have to trust three parties to ensure uniqueness of
  74. your IDs:
  75. - Objective Development, that they don't give the same PID to more than
  76. one person.
  77. - The owner of the Vendor-ID that they don't assign PIDs from the range
  78. assigned to Objective Development to anybody else.
  79. - Usb.org that they don't assign the same Vendor-ID a second time.
  80. ==================================
  81. WHO IS THE OWNER OF THE VENDOR-ID?
  82. ==================================
  83. Objective Development has obtained ranges of USB Product-IDs under two
  84. Vendor-IDs: Under Vendor-ID 5824 from Wouter van Ooijen (Van Ooijen
  85. Technische Informatica, www.voti.nl) and under Vendor-ID 8352 from Jason
  86. Kotzin (Clay Logic, www.claylogic.com). Both VID owners have received their
  87. Vendor-ID directly from usb.org.
  88. =========================================================================
  89. CAN I USE USB-IDs FROM OBJECTIVE DEVELOPMENT WITH OTHER DRIVERS/HARDWARE?
  90. =========================================================================
  91. The short answer is: Yes. All you get is a guarantee that the IDs are never
  92. assigned to anybody else. What more do you need?
  93. ============================
  94. WHAT ABOUT SHARED ID PAIRS?
  95. ============================
  96. Objective Development has reserved some PID/VID pairs for shared use. You
  97. have no guarantee of uniqueness for them, except that no USB compliant device
  98. uses them. In order to avoid technical problems, we must ensure that all
  99. devices with the same pair of IDs use the same driver on kernel level. For
  100. details, see the file USB-IDs-for-free.txt.
  101. ======================================================
  102. I HAVE HEARD THAT SUB-LICENSING OF USB-IDs IS ILLEGAL?
  103. ======================================================
  104. A 16 bit integer number cannot be protected by copyright laws. It is not
  105. sufficiently complex. And since none of the parties involved entered into the
  106. USB-IF Trademark License Agreement, we are not bound by this agreement. So
  107. there is no reason why it should be illegal to sub-license USB-IDs.
  108. =============================================
  109. WHO IS LIABLE IF THERE ARE INCOMPATIBILITIES?
  110. =============================================
  111. Objective Development disclaims all liabilities which might arise from the
  112. assignment of IDs. If you guarantee product features to your customers
  113. without proper disclaimer, YOU are liable for that.