TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Anybody dealing with the VID/PID USB issue for small open source projects?

1 pointsby mofosyneabout 10 years ago
Anyone dealing with the VID&#x2F;PID issue for opensource projects? E.g. Start a Open Serial Bus org perhaps to highjack some abandoned VID spaces?<p>--------<p>If I recall, USB-IF is pretty hostile to small players distributing only a few products like open sourced projects.<p>I wonder if there has been any progress in this matter. If not... then has there been any efforts to at least hijack a VID space from a dead company, and coordinate the distribution of the PID numbers for open sourced projects.<p>On dealing with the USB markings, is it possible to perhaps design a logo that is different enough from the logo USB, but is distinct enough to not be a legal concern?<p>If so, then we should call this logo &quot;Open Serial Bus&quot;, maybe the shape of the logo could be a silhouette of a usb plug, but superimposed over the open hardware lock&amp;gears.<p>----<p>While we are at it, might be also nice to provide a consistent method for non-standard signals to interface with such &quot;Open Serial Bus&quot; devices. E.g. I saw some phone re-purposed the micro usb connectors to enable or output TTL serial pin outs in place of D+ &amp; D- with a special signal to the ID pin. Sounds very useful. (In that particular case, perhaps a one wire eeprom with baud rate settings might be helpful on the ID pin)<p>-------<p>Btw &quot;Open Serial Bus&quot; does not mean USB. It is OSB. Especially since such org cannot provide guarantees that USB-IF wouldn&#x27;t do anything to cause trouble (e.g. reissuing a revoked VID&#x2F;PID pair). And trademark wise, it is OSB, not USB, and thus is not likely to be confused by consumers (Especially if the logo is kept distinct).<p>You should also have a strict admittance system to ensure only open source projects are included (at the very least to reduce the incentive for USB-IF to take additional offensive measures).<p>There is precedence for this however. If you recall about i2c, other companies decide to call compatible implementations as TWI (two wire interface) to avoid paying licencing fees.<p>USB-IF will not be losing money from this however, since if you are making a normal commercial product (with sizable number of items to sell), you ought to fork up the fee to USB-IF to ensure your product is kosher anyway.<p>tl;dr: Open, but not Universal. But better than the alternative of forking up $5k for a small open source product.

no comments

no comments