pidcodes / pidcodes.github.com Goto Github PK

After the initial pull request for CombineReality (#555 ) failed because of extra website link and mismatching names (extra spaces) under org. We corrected the issue a few days after issue closed by moderator, but were no longer able to send anymore pull requests. How can we fix this?

For example, my org is listed (FrozenElectronics), but the PID I was assigned (5555) is not. Some of the other entries are out of order; l0pthware's PIC32 board is at the very bottom of the list for me despite starting with a C.

Not sure if this is because of the recent massive PR (thanks @tannewt and #554 !!!) but something is definitely a bit weird with the site.

Shouldn't the repo name be pidcodes.github.io or pid.codes? pidcodes.github.com is a 404.

Have you thought about allocating one of the spare identifiers to mean something like "The vendor name string for this product should be parsed and contains a '#' followed by a UUID in hex" so every obscure random weird widget has a way to bind at least on free operating systems without needing to take up a pidcodes identifier ?

At that point for open systems at least it ought to then scale near infinitely and without intervention

Alan

GitHub Pages now supports HTTPS on custom domain names. Enabling it is easy.

Hi @Arachnid

We have seen this great project has stopped, we know that it may be too much work for one person to review so many projects, would you be willing to receive help or can we know if there is some other problem for which new projects have not been accepted?

@tannewt has offered his help (example pullrequest #554 ) and I can help too if you allow it

We look forward to getting a response from you.

regards

It appears the options for the html proofer check are out of date for 4.2.0

This error happens when checking my PR #753

"htmlproofer 4.2.0 | Error: invalid option: --internal-domains=pid.codes"

gjtorikian/html-proofer@v4.1.0...v4.2.0

I bereave that the the following VID are candidates that are save to include in this project through mergers, bankruptcy, shutdown there operations, etc.
the VID with a star ( * ) on the end are most likely to be save to include in this project.
bankruptcy/shutdown or mergers that was more than 10 years at go.

0430 Sun Microsystems, Inc.
045d Nortel Networks, Ltd *
04a0 Digital Equipment Corp *
04ab Chromatic Research *
051a WYSE Technology
059b Iomega Corp *
08b9 RadioShack Corp. (Tandy) *
0830 Palm, Inc.
08c8 2Wire, Inc.
0b62 Orange Micro, Inc. *
0bc7 X10 Wireless Technology, Inc.
0e22 Symbian Ltd.
12ef Tapwave, Inc. *

The database Linux-based desktop systems use to describe USB devices in lsusb is accessed (through the detour of udev's database maintained at systemd but updated from there) as usb.ids and maintained at https://usb-ids.gowdy.us/.

Is there a regular batch process (possibly automated using mail submit) that is run on the pidcodes data? If so, that could be stated somewhere (if only in this ticket), and if not too, for then applicants can know to just submit their items to https://usb-ids.gowdy.us/ once they're allocated, without fear of upsetting some process.

The current directories aren't sorting nicely as some are caps, and some are lower case.

Would a all caps/lowercase pull request be accepted?

Not that it matters in the slightest, but this document from USB-IF lists 0x1209 as an obsolete VID. The link from their "Information for Developers" page says "The VIDs included on this list have been obsoleted and are not valid."

0x1209 is 4617 in decimal. I can't begin to fathom why they thought decimal was the right choice for that column.

If nothing else, the part of the main pid.codes webpage that says "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." should probably make mention of this fact, just in case some USB host implementation out there actually blacklists obsoleted VIDs.

This suggestion seeks reserving 16 PIDs as class-generic PIDs that is suitable for devices implementing one of the five most frequently used device classes that most modern operating systems carry device class drivers, or a combination of them in a composite device:

• USB HID,
• USB MSC (Flash drives)
• USB CDC ACM (USB Serial)
• USB CDC NCM (USB Ethernet)
• USB DFU (bootloaders, special case in PID allocation)

The 16 reserved PIDs share the same high nibbles, and form a 4-bit bitfield in the lowest nibble of the PID. Setting the bit means the function in question exists in the device exactly once, and clearing it means the function does not exist in the device. The bit allocations are:

• HID = 0b0001,
• MSC = 0b0010
• CDC_ACM = 0b0100,
• CDC_NCM = 0b1000

A special case is made when all four bits are zero. This PID indicates a class-generic USB DFU device, intended to be used by bootloaders.

In this way each class-generic PID corresponds to exactly one USB device driver or one combination of them. Devices using those class-generic PIDs have to distinguish from each other using other methods, for example USB strings, serial numbers, or HID report descriptors. They also must work with the default driver shipped in most modern operating systems (user-mode applications does not count as drivers.)

Think we could add pid.codes to the relevant metadata packages? Currently 1209 lists as "Generic" which isn't wrong, but might be nice to do some passive advertising for this project 🤗.

For a single device, I have:

• different licenses for firmware and hardware (e.g. Artistic-2.0 and CERN OHL 1.2)
• several source repos (e.g. firmware_old, firmware_new, PCB1, PCB2, hardware1, hardware2).

How should I handle this in the index.md?

Hello. I was sent here from the adafruit circuitpython page.

I am currently following this guide: https://learn.adafruit.com/how-to-add-a-new-board-to-circuitpython/overview

so that guide requires VID/PID in order to release the software.. but you require the software before i can get a VID/PID?

so i dont know what to do.

I'm using MacOS Ventura 13.6.1 and my STM32 HID flashing tool (https://pid.codes/1209/BABE/) has stopped working on it. Anyone else having similar issues under latest versions of MacOS?

Hi,

I want to change the Product ID and Vendor ID of my Raspy Pico. After some research I found the TinyUSB library and there seems to be settings for Device Descriptor. As soon as I integrate the library in my program however, the USB doesn´t show up on my Device Manager anymore (device manager isn´t even refreshing when I plug the raspy in). I want the raspberry to show up under "USB controller" with a custom PID, VID and device descripton. I´m programing in C in Visual Studio Code on Windows. Is there an example on how to change the PID, VID and device descripton?

Thanks.

• Check Open Graph via html-proofer gjtorikian/html-proofer#111
• Check tags when html-proofer supports HTML 5 gjtorikian/html-proofer#362
• Fail on broken external URLs #200
• Ensure people use the correct filename/folder format #196
• Confirm the link validation will catch people giving their org folder the wrong name
• Switch to checking the owner/org in markdown - revert #198
• Turn Jekyll build warnings into failures https://travis-ci.org/pidcodes/pidcodes.github.com/jobs/195217329#L342
• Validate layout options e.g. https://travis-ci.org/pidcodes/pidcodes.github.com/jobs/195217329#L342 and astrojr1@91d3de5

Hi! I'm a developer working on CircuitPython for Adafruit. I noticed that you've been unable to approve new codes for the past few months. Would it be possible for me to help you out by reviewing these PRs to make sure they fit your guidelines? Is there some other way I can help?

I'd like to suggest to reserve a special PID for an idea I've been toying around lately (not for my use, but for everyone): One thing I never understood about the USB spec is, why Intel and Microsoft, who love GUIDs (look at OLE(2), COM and so on) used short 2·16 bit IDs for USB. The only explanation was/is, that this is a form of a cash grab. USB would have been just as easy to implement using GUIDs for vendor and product.

So the idea I had is the following: USB descriptors can carry additional data to the standard defined fields. Also there is support for arbitrary string descriptors. Reserving a special VID:PID pair could be associated with a custom "specification" that the actual vendor and product ID are to be retrieved from a dedicated string descriptor in the form of GUIDs. I've been doing this for some time now with VID:PID=0:0. I'd like to see that idea to spread.

Why are some pull requests that been waiting for awhile for reviews aren't getting reviewed but yet some coming in NEW are getting them in less than an hour or a day?

There are two files in the main directory:

• LICENSE implying CC0
• LICENSE.txt implying MIT

LICENSE.txt was commited one day after LICENSE. Both in the very early days of the repository. However, I don't seem to find documentation which one is actually in use.

Maybe this ist just a clean-up thing. Still it is a bit confusing. With the younger file being MIT license, I guess the intent is MIT, and to err on the side of compliance it's probably better to assume the more restrictive. Nevertheless, github's view license link on the right links to the CC0 version.