Update allocated-pids.txt #127
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks good, merged! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"A short description of what the device is going to do (e.g. cat tracker with USB trace download)":
Family of USB-devices with accessibility features: Keyboard, Mouse, MIDI-Controllers, Game-controllers. Bluetooth as option.
"What chip are you using for the device the PID is allocated for (e.g. ESP32-S2)":
ESP32-S3 (USB/Bluetooth)
ESP32-S2 (USB)
"Why you need a custom PID (and can't, for instance, use the default TinyUSB PIDs)":
For device identification, events filtering and prevent conflicts with other devices.
"If you're requesting a PID on behalf of a company, please mention the name of the company":
Ultradrom
"If applicable/available, a website or other URL with information about your product or company":
ultradrom.com