Menu
▾
▴
Re: [Libusb-devel] USB VID/PID for open source projects
|
From: Тихомиров В. <int...@ya...> - 2011-03-24 17:35:45
|
I feel it is a waste of of VIDs for the small companies, which is a majority, to order a 65535-device VID for their two devices. I wonder why nobody so far implemented my idea - purchasing a VID and selling the PIDs. It would be a good business, I'm sure. Additionally, Vid/Pid address space would be optimized and small developers satisfied. > There is one more issue for the test firmware which is a common issue for small USB developers. Sometimes you can get a free PID sub-licensed from the vendors like FTDI, TI/Luminary and Microchip. And we indeed get one for our Microchip based test firmware (thanks a lot again, Microchip!). But they all have strings attached -- to be used with vendors' USB parts only. Texas Instruments have rejected my request telling that their agreement does not let them to. I suppose they refer to the VID ownership right, obtained from USB-IF. Valentin. 24.03.2011, 19:48, "Greg KH" <gr...@kr...>: > On Thu, Mar 24, 2011 at 10:34:39AM +0800, Xiaofan Chen wrote: > >> For libusb-win32 project, we have a few issues and some of them >> have been sorted out, for example, the kernel driver signing issue >> which has been solved by the generous donations of the people >> in the libusb/libusb-win32 mailing list. For the issues with >> GPL being excluded license for WHQL we are also working >> on it (to change the kernel driver license to BSD in the future). >> >> There is one more issue for the test firmware which is a common >> issue for small USB developers. Sometimes you can get a free >> PID sub-licensed from the vendors like FTDI, TI/Luminary and >> Microchip. And we indeed get one for our Microchip based >> test firmware (thanks a lot again, Microchip!). But they all have >> strings attached -- to be used with vendors' USB parts only. >> >> Now we intend to have more broader test firmware available, >> for example, for Cypress EZ-USB FX2/FX2LP (high speed >> USB) and Atmel AVR (and probably AVR32 with high speed) >> and ARM MCUs. Then we can not use the Microchip VID/PID. >> >> What are the potential solution here? I think it is too expensive >> to get a USB VID for small projects like libusb/libusb-win32. >> >> And I do not really like to use random USB VID/PID like >> what we do right now -- that is the motivation to get a >> valid PID in the first place. > > For Linux-based projects, I can assign valid product id numbers from the > Linux Foundation's vendor id. Just email me and let me know what you > want/need and I will reserve it. > > For non-Linux-based projects, sorry, I don't know what to suggest. > > thanks, > > greg k-h > > ------------------------------------------------------------------------------ > Enable your software for Intel(R) Active Management Technology to meet the > growing manageability and security demands of your customers. Businesses > are taking advantage of Intel(R) vPro (TM) technology - will your software > be a part of the solution? Download the Intel(R) Manageability Checker > today! http://p.sf.net/sfu/intel-dev2devmar > _______________________________________________ > Libusb-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-devel |
