Files
pidcodes.github.com/about.md
Peter Newman 3706846b8a Enable initial Travis CI workflow (#183)
* Remove errant .DS_Store file

* Ignore .DS_Store

* Create a list of organisations

* Add an org list

* Show number of PIDs per org

* Fix HTML issue, sort orgs by title

* Try and fix the PID count

* Try and fix issues

* Try again to fix issues

* Try yet again to fix issues

* Correct the urlpart

* Change to sort_natural, minor code tidy

* Try and fix the sorting

* Try again to fix the sorting

* Remove debugging

* Add a link to orgs page

* Install dependencies for Travis

* Create .travis.yml

* Add the Travis script

* Update the Ruby version

* Bump the Ruby version some more

* Switch back to the documented version

* Add the exclude

* Update based on https://github.com/jekyll/jekyll/pull/5413

* Add github-pages Gem

* Add missing gems

* Add redcarpet

* Switch to tasks so we can run multiple CI tasks

* Switch to tasks

* Fix the matrix

* More matrix fixing

* Turn on more htmlproofer options

* Make the check less strict

* Don't bother complaining about extra jekyll tags

* Escape HTML entities

* Fix the email link

* Fix the link within the 404 page!

* Escape more HTML entities

* Remove an invalid site URL

* Cache ruby bundles

* Escape even more HTML entities

* Escape yet more HTML entities

* Escape more HTML entities and switch to a div

* Try and fix the errant paragraph item

* Add a Travis badge to the readme

* Update Gemfile

Adapted from https://github.com/lunaryorn/lunaryorn.github.io

* Update _config.yml

* Add some more checks to Travis

* Report GH Pages versions

* Tidy up, add redcarpet back in

* Try and stop the spurious paragraph tags
2016-10-02 12:55:08 +01:00

1.6 KiB

layout, title, permalink
layout title permalink
page About pid.codes /about/

If you're a maker, hobbyist, or startup company producing your own USB device, you'll need a USB Vendor ID and Product ID to uniquely identify your device to computers. The USB-IF's position is that the only way to do this is for each organisation to pay $5000 for a unique Vendor ID, which may not be shared with other individuals or organisations.

For many makers and small companies, this is a prohibitive amount of money, and forces them to resort to workarounds, such as using other organisations' VIDs without permission, or simply making up a VID and PID. These solutions make things worse for everyone, by damaging the assumption that a VID/PID combination is unique to a given device.

pid.codes seeks to solve this issue for anyone producing open-source hardware. We have been gifted a Vendor ID by a company that was issued one by USB-IF and has since ceased trading; they obtained the Vendor ID before the USB-IF changed their licensing terms to prohibit transfers or subassignments.

pid.codes will assign PIDs on any VID we own to any open-source hardware project needing one. To learn how to get a PID or PIDs for your project, see the how to get a PID page.

pid.codes will also gladly accept donations of Vendor IDs from other organisations that no longer require them, and take responsibility for administering them. If you have a VID code that is no longer in use, please contact us at admin@pid.codes.

This site is in no way supported or endorsed by USB-IF.