Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update allocated-pids.txt #167

Merged
merged 3 commits into from
Jul 28, 2024
Merged

Update allocated-pids.txt #167

merged 3 commits into from
Jul 28, 2024

Conversation

JimDrewGH
Copy link
Contributor

Requesting PID for SuperCard Pro Deluxe controller.

CBMSTUFF.COM

Requesting PID for SuperCard Pro Deluxe controller. 

CBMSTUFF.COM
@Spritetm
Copy link
Member

  • Could you perhaps attempt to answer the questions stated in the README.md of this repo?
  • The PIDs are hexadecimal, so the next one in line is 0x821A.

@JimDrewGH
Copy link
Contributor Author

Sorry, but I thought I answered the questions:

A short description of what the device is going to do (e.g. cat tracker with USB trace download)

SuperCard Pro Deluxe

What chip are you using for the device the PID is allocated for (e.g. ESP32-S2)

ESP32-S3

Why you need a custom PID (and can't, for instance, use the default TinyUSB PIDs)

So device name and manufacturer appears in the USB information when polling the USB system.

If you're requesting a PID on behalf of a company, please mention the name of the company

CBMSTUFF.COM

If applicable/available, a website or other URL with information about your product or company

CBMSTUFF.COM

Yes, I realize now that the ID's were hex and just skipped from 8219 to 8220, so I will correct that.

@Spritetm
Copy link
Member

Looks good now, the fail is a CI error because the original lacked a newline. I've merged, thanks!

@Spritetm Spritetm merged commit 276686e into espressif:main Jul 28, 2024
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants