[Discuss] Current status of USB VID/PID for open source hardware?

malcolm stanley a.malcolm.stanley at gmail.com
Mon Nov 4 23:06:47 UTC 2013


are the 2013 videos up yet?

_________________________________________
malcolm stanley

google.voice:  215.821.6252
Cell: 267.251.9479   <------------- new
email: a.malcolm.stanley at gmail.com
twitter / linkedin: amstanley
Read my blog at http://soaringhorse.blogspot.com
_________________________________________


On Mon, Nov 4, 2013 at 11:39 AM, Catarina Mota
<catarina at openmaterials.org>wrote:

> Yup, here's the video of Ian's talk at the OHS last year:
> https://vimeo.com/63986266
>
>
> On Mon, Nov 4, 2013 at 2:37 PM, Mike Hord <mike.hord at sparkfun.com> wrote:
>
>> Ian from Dangerous Prototypes gave a very insightful presentation about
>> the nightmares involved in this at the 2012 OHS.
>>
>>
>> http://dangerousprototypes.com/2012/10/03/open-hardware-summit-2012-usb-and-open-hardware-presentation/
>>
>> Mike
>>
>>
>> On Mon, Nov 4, 2013 at 12:34 PM, David A. Mellis <dam at mellis.org> wrote:
>>
>>> Hey all,
>>>
>>> This is an important issue and one the OSHWA board is interested in. As
>>> a first step, I thought it would be good to include a discussion of the USB
>>> VID/PID issues in the open-source hardware FAQ and best practices document
>>> on the OSHWA website.
>>>
>>> Anyone have any good pointers to existing information on the topic that
>>> I should reference or link to?  Any specific questions / issues you'd like
>>> to see addressed in the write up?
>>>
>>> Anyone have any contacts with the USB IF or other relevant parties? We'd
>>> like to work on outreach to them.
>>>
>>> David
>>>
>>>
>>> On Sun, Oct 20, 2013 at 7:47 PM, Andrew Stone <stone at toastedcircuits.com
>>> > wrote:
>>>
>>>> Squat on VID f055 (get it? :-)).  This will make this VID unassignable
>>>> and is actually better for the consortium than ppl choosing a random VID
>>>> because the other VIDs remain unused.  No one has the legal right to
>>>> control what bits you send over the wire... they can only control your use
>>>> of the usb logo. IANAL IANYL this is not legal advice blah blah...
>>>>
>>>>   Use random pid and your driver can verify the product name string to
>>>> avoid any possible conflicts.
>>>> On Oct 20, 2013 5:52 PM, "Adam Fabio" <afabio at gmail.com> wrote:
>>>>
>>>>>  Hi Everyone,
>>>>> Disclosure - I'm a member of the open source hardware community, and
>>>>> also an author for Hackaday. I'm doing a bit of research for an article
>>>>> about USB VID/PID $5000 cost and open source hardware. Nick Johnson of a
>>>>> Arachnid Labs posted a blog entry about the issue recently, and the
>>>>> reception he received when asking the USB-IF about the issue was cold to
>>>>> say the least.
>>>>>
>>>>> http://www.arachnidlabs.com/blog/2013/10/18/usb-if-no-vid-for-open-source/
>>>>>
>>>>> I know the openMoko project here:
>>>>> http://wiki.openmoko.org/wiki/USB_Product_IDs is an option.
>>>>>
>>>>> Is OSHWA communicating with the USB-IF on this issue?  If so, what
>>>>> direction are they headed?
>>>>>
>>>>> Thanks,
>>>>> Adam Fabio
>>>>>
>>>>> _______________________________________________
>>>>> discuss mailing list
>>>>> discuss at lists.oshwa.org
>>>>> http://lists.oshwa.org/listinfo/discuss
>>>>>
>>>>>
>>>> _______________________________________________
>>>> discuss mailing list
>>>> discuss at lists.oshwa.org
>>>> http://lists.oshwa.org/listinfo/discuss
>>>>
>>>>
>>>
>>> _______________________________________________
>>> discuss mailing list
>>> discuss at lists.oshwa.org
>>> http://lists.oshwa.org/listinfo/discuss
>>>
>>>
>>
>> _______________________________________________
>> discuss mailing list
>> discuss at lists.oshwa.org
>> http://lists.oshwa.org/listinfo/discuss
>>
>>
>
> _______________________________________________
> discuss mailing list
> discuss at lists.oshwa.org
> http://lists.oshwa.org/listinfo/discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oshwa.org/pipermail/discuss/attachments/20131104/60170b11/attachment.html>


More information about the discuss mailing list