micropython / micropython/micropython
What to do about USB VID and PID?
Open
Nobody has claimed this yet.
port-stm32
rfc
- Dominant language
- C
- Stars
- 22.1k
- Forks
- 9k
- Avg merge
- 6d 4h
- Merged PRs (30d)
- 16
Description
As @chrismas9 pointed out to me, there are a few options, none of which are optimal:
- Buy your own VID from USB-IF for $US5000.
- Request free PIDs from Openmoko http://wiki.openmoko.org/wiki/USB_Product_IDs
- Buy PIDs from MCS Electronics for EUR9.95. Their VID has been revoked so they are only selling a guarantee that no one else will have the same PID.
- Use VID=0xf055; see http://hackaday.com/2013/10/22/usb-implementers-forum-says-no-to-open-source/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the four VID/PID options listed in the issue and determine which decision the project needs; done requires an agreed allocation and clear follow-up scope, neither of which is specified here.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100