USBID-License.txt 7.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146
  1. Royalty-Free Non-Exclusive License USB Product-ID
  2. =================================================
  3. Version 2008-04-07
  4. OBJECTIVE DEVELOPMENT Software GmbH hereby grants you the non-exclusive
  5. right to use three USB.org vendor-ID (VID) / product-ID (PID) pairs with
  6. products based on Objective Development's firmware-only USB driver for
  7. Atmel AVR microcontrollers:
  8. * VID = 5824 (=0x16c0) / PID = 1500 (=0x5dc) for devices implementing no
  9. USB device class (vendor-class devices with USB class = 0xff). Devices
  10. using this pair will be referred to as "VENDOR CLASS" devices.
  11. * VID = 5824 (=0x16c0) / PID = 1503 (=0x5df) for HID class devices
  12. (excluding mice and keyboards). Devices using this pair will be referred
  13. to as "HID CLASS" devices.
  14. * VID = 5824 (=0x16c0) / PID = 1505 (=0x5e1) for CDC class modem devices
  15. Devices using this pair will be referred to as "CDC-ACM CLASS" devices.
  16. * VID = 5824 (=0x16c0) / PID = 1508 (=0x5e4) for MIDI class devices
  17. Devices using this pair will be referred to as "MIDI CLASS" devices.
  18. Since the granted right is non-exclusive, the same VID/PID pairs may be
  19. used by many companies and individuals for different products. To avoid
  20. conflicts, your device and host driver software MUST adhere to the rules
  21. outlined below.
  22. OBJECTIVE DEVELOPMENT Software GmbH has licensed these VID/PID pairs from
  23. Wouter van Ooijen (see www.voti.nl), who has licensed the VID from the USB
  24. Implementers Forum, Inc. (see www.usb.org). The VID is registered for the
  25. company name "Van Ooijen Technische Informatica".
  26. RULES AND RESTRICTIONS
  27. ======================
  28. (1) The USB device MUST provide a textual representation of the
  29. manufacturer and product identification. The manufacturer identification
  30. MUST be available at least in USB language 0x0409 (English/US).
  31. (2) The textual manufacturer identification MUST contain either an Internet
  32. domain name (e.g. "mycompany.com") registered and owned by you, or an
  33. e-mail address under your control (e.g. "myname@gmx.net"). You can embed
  34. the domain name or e-mail address in any string you like, e.g. "Objective
  35. Development http://www.obdev.at/avrusb/".
  36. (3) You are responsible for retaining ownership of the domain or e-mail
  37. address for as long as any of your products are in use.
  38. (4) You may choose any string for the textual product identification, as
  39. long as this string is unique within the scope of your textual manufacturer
  40. identification.
  41. (5) Matching of device-specific drivers MUST be based on the textual
  42. manufacturer and product identification in addition to the usual VID/PID
  43. matching. This means that operating system features which are based on
  44. VID/PID matching only (e.g. Windows kernel level drivers, automatic actions
  45. when the device is plugged in etc) MUST NOT be used. The driver matching
  46. MUST be a comparison of the entire strings, NOT a sub-string match. For
  47. CDC-ACM CLASS and MIDI CLASS devices, a generic class driver should be used
  48. and the matching is based on the USB device class.
  49. (6) The extent to which VID/PID matching is allowed for non device-specific
  50. drivers or features depends on the operating system and particular VID/PID
  51. pair used:
  52. * Mac OS X, Linux, FreeBSD and other Unixes: No VID/PID matching is
  53. required and hence no VID/PID-only matching is allowed at all.
  54. * Windows: The operating system performs VID/PID matching for the kernel
  55. level driver. You are REQUIRED to use libusb-win32 (see
  56. http://libusb-win32.sourceforge.net/) as the kernel level driver for
  57. VENDOR CLASS devices. HID CLASS devices all use the generic HID class
  58. driver shipped with Windows, except mice and keyboards. You therefore
  59. MUST NOT use any of the shared VID/PID pairs for mice or keyboards.
  60. CDC-ACM CLASS devices require a ".inf" file which matches on the VID/PID
  61. pair. This ".inf" file MUST load the "usbser" driver to configure the
  62. device as modem (COM-port).
  63. (7) OBJECTIVE DEVELOPMENT Software GmbH disclaims all liability for any
  64. problems which are caused by the shared use of these VID/PID pairs. You
  65. have been warned that the sharing of VID/PID pairs may cause problems. If
  66. you want to avoid them, get your own VID/PID pair for exclusive use.
  67. HOW TO IMPLEMENT THESE RULES
  68. ============================
  69. The following rules are for VENDOR CLASS and HID CLASS devices. CDC-ACM
  70. CLASS and MIDI CLASS devices use the operating system's class driver and
  71. don't need a custom driver.
  72. The host driver MUST iterate over all devices with the given VID/PID
  73. numbers in their device descriptors and query the string representation for
  74. the manufacturer name in USB language 0x0409 (English/US). It MUST compare
  75. the ENTIRE string with your textual manufacturer identification chosen in
  76. (2) above. A substring search for your domain or e-mail address is NOT
  77. acceptable. The driver MUST NOT touch the device (other than querying the
  78. descriptors) unless the strings match.
  79. For all USB devices with matching VID/PID and textual manufacturer
  80. identification, the host driver must query the textual product
  81. identification and string-compare it with the name of the product it can
  82. control. It may only initialize the device if the product matches exactly.
  83. Objective Development provides examples for these matching rules with the
  84. "PowerSwitch" project (using libusb) and with the "Automator" project
  85. (using Windows calls on Windows and libusb on Unix).
  86. Technical Notes:
  87. ================
  88. Sharing the same VID/PID pair among devices is possible as long as ALL
  89. drivers which match the VID/PID also perform matching on the textual
  90. identification strings. This is easy on all operating systems except
  91. Windows, since Windows establishes a static connection between the VID/PID
  92. pair and a kernel level driver. All devices with the same VID/PID pair must
  93. therefore use THE SAME kernel level driver.
  94. We therefore demand that you use libusb-win32 for VENDOR CLASS devices.
  95. This is a generic kernel level driver which allows all types of USB access
  96. for user space applications. This is only a partial solution of the
  97. problem, though, because different device drivers may come with different
  98. versions of libusb-win32 and they may not work with the libusb version of
  99. the respective other driver. You are therefore encouraged to test your
  100. driver against a broad range of libusb-win32 versions. Do not use new
  101. features in new versions, or check for their existence before you use them.
  102. When a new libusb-win32 becomes available, make sure that your driver is
  103. compatible with it.
  104. For HID CLASS devices it is necessary that all those devices bind to the
  105. same kernel driver: Microsoft's generic USB HID driver. This is true for
  106. all HID devices except those with a specialized driver. Currently, the only
  107. HIDs with specialized drivers are mice and keyboards. You therefore MUST
  108. NOT use a shared VID/PID with mouse and keyboard devices.
  109. Sharing the same VID/PID among different products is unusual and probably
  110. violates the USB specification. If you do it, you do it at your own risk.
  111. To avoid possible incompatibilities, we highly recommend that you get your
  112. own VID/PID pair if you intend to sell your product. Objective
  113. Development's commercial licenses for AVR-USB include a PID for
  114. unrestricted exclusive use.