I wasn't having any issues, was just curious as this is a common problem I run into with many of my projects. I'm all for squatting on a VID, the $5,000 price tag for a VID from USB-IF is insane. In the past I've used 0xF055, but its good to know that 0xFFFE is also being squatted on by FOSS projects.
On Tue, May 3, 2016 at 5:22 PM Bdale Garbee <[email protected]> wrote: > Jared Szechy <[email protected]> writes: > > > I noticed that all the devices use a USB VID of 0xfffe. I'm going to > guess > > this has not been registered with USB-IF, since their highest issued VID > is > > 0x2700. > > Correct. Is this causing you any difficulty, or is your question just > for interest? > > In either case, a number of us working on Free Hardware projects decided > at one point to "squat" at the top of the USB VID address space rather > than pay the ridiculous fee to register an official VID. Eric Blossom > manages allocations of PIDs in the 0xfffe VID so that we don't create > any overlaps. We currently occupy two PID ranges, allocated as follows: > > #define USB_VID_FSF 0xfffe // Free Software Folks > > #define USB_PID_Development 0x000a // Bdale Garbee <[email protected]> > #define USB_PID_TeleMetrum 0x000b // Bdale Garbee <[email protected]> > #define USB_PID_TeleDongle 0x000c // Bdale Garbee <[email protected]> > #define USB_PID_TeleTerra 0x000d // Bdale Garbee <[email protected]> > #define USB_PID_TeleBT 0x000e // Bdale Garbee <[email protected]> > #define USB_PID_TeleLaunch 0x000f // Bdale Garbee <[email protected]> > #define USB_PID_TeleLCO 0x0010 // Bdale Garbee <[email protected]> > #define USB_PID_TeleScience 0x0011 // Bdale Garbee <[email protected]> > #define USB_PID_TelePyro 0x0012 // Bdale Garbee <[email protected]> > #define USB_PID_TeleShield 0x0013 // Bdale Garbee <[email protected]> > #define USB_PID_TeleMega 0x0023 // Bdale Garbee <[email protected]> > #define USB_PID_MegaDongle 0x0024 // Bdale Garbee <[email protected]> > #define USB_PID_TeleGPS 0x0025 // Bdale Garbee <[email protected]> > #define USB_PID_EasyMini 0x0026 // Bdale Garbee <[email protected]> > #define USB_PID_TeleMini 0x0027 // Bdale Garbee <[email protected]> > #define USB_PID_EasyMega 0x0028 // Bdale Garbee <[email protected]> > #define USB_PID_USBtrng 0x0029 // Bdale Garbee <[email protected]> > #define USB_PID_USBrelay 0x002a // Bdale Garbee <[email protected]> > #define USB_PID_MicroPeakUSB 0x002b // Bdale Garbee <[email protected]> > #define USB_PID_FSF_BDALE_19 0x002c // Bdale Garbee <[email protected]> > > Since the only point of the VID/PID space is to allow devices to be > uniquely identified, and there are no known conflicts, there's no > particular reason for us to change anything. I'm pretty sure if we were > starting over today, we'd choose to sublicense PIDs... but the whole > idea of "pay to play" to get unique integers defined is just nuts and > I'm happy to be seen as a conscientious objector by using 0xfffe here. > > Note that for our upcoming hardware random number generator, ChaosKey, > which we think it's possible will ship in higher volumes than our > existing products and to a broader range of potential users, Keith *did* > go register with Openmoko for a PID: > > PRODUCT=ChaosKey-v0.1 > IDVENDOR=0x1d50 > IDPRODUCT=0x60c6 > > Also, thanks to Keith's hard work, a driver for this device has already > been accepted into the upstream Linux kernel source tree, so once we > have these ready to ship, users of recent Linux kernels will enjoy a > true plug and play "it just works" experience... ;-) > > Regards, > > Bdale >
_______________________________________________ altusmetrum mailing list [email protected] http://lists.gag.com/mailman/listinfo/altusmetrum
