From: Patrick Maupin <pmaupin@gmail.com>
To: esr@thyrsus.com
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] Build vs. modify vs. what should we be doing anyway?
Date: Mon, 12 Mar 2012 17:10:14 -0500 [thread overview]
Message-ID: <CAPz3yKfsQVmQYwU7YTVmQZrieGWov2gfEg_wqn18ROP7FqKBPA@mail.gmail.com> (raw)
In-Reply-To: <20120312213946.GE17895@thyrsus.com>
On Mon, Mar 12, 2012 at 4:39 PM, Eric S. Raymond <esr@thyrsus.com> wrote:
> Sorry, my eyes aren't educated enough. (I'm an ex-mathematician; what
> relatively little I know about electronics design I've picked up by
> osmosis doing software). What does it say?
It says:
I am a very simple board. My major components are:
- USB module
- USB patch antenna
- Small PL2303 clone (fitting in with your lawsuit theory)
- Simple 5v -> 3.3v voltage regulator
- Coin cell battery
- Diode so as not to drain battery during operation
- USB connector
There is nothing there that would require 4 layers, and all the
traces seem to "go somewhere".
There doesn't seem to be a real 8 pin SOIC PL2303.
It almost certainly isn't illegal to clone one of these chips
(although there might be an infringed patent or two there, that isn't
necessarily true either). It probably is illegal to exhort people to
download the copyrighted Windows PL2303 driver and use it with this.
Probably not a problem with Linux :-)
next prev parent reply other threads:[~2012-03-12 22:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 18:02 Patrick Maupin
2012-03-12 21:03 ` Eric S. Raymond
2012-03-12 21:18 ` tz
2012-03-12 21:26 ` Eric S. Raymond
2012-03-12 21:28 ` Patrick Maupin
2012-03-12 21:39 ` Eric S. Raymond
2012-03-12 22:10 ` Patrick Maupin [this message]
2012-03-12 22:23 ` tz
2012-03-12 22:33 ` Patrick Maupin
2012-03-13 2:29 ` Ron Frazier (NTP)
2012-03-13 2:39 ` Chris Kuethe
2012-03-12 22:45 ` Eric S. Raymond
2012-03-12 23:01 ` Dave Taht
2012-03-13 1:43 ` Eric S. Raymond
2012-03-13 2:04 ` Chris Kuethe
2012-03-13 2:13 ` Eric S. Raymond
2012-03-13 2:40 ` Dave Taht
2012-03-13 2:53 ` Chris Kuethe
2012-03-13 4:54 ` Eric S. Raymond
2012-03-13 13:23 ` Dave Taht
2012-03-13 14:35 ` tz
2012-03-13 16:04 ` Eric S. Raymond
2012-03-13 16:22 ` tz
2012-03-13 2:38 ` Ron Frazier (NTP)
2012-03-13 2:42 ` Chris Kuethe
2012-03-13 3:00 ` Ron Frazier (NTP)
2012-03-13 3:04 ` Dave Taht
2012-03-13 3:06 ` Chris Kuethe
2012-03-13 3:16 ` Dave Taht
2012-03-13 3:31 ` Chris Kuethe
2012-03-13 4:49 ` Dave Taht
2012-03-13 4:55 ` Eric S. Raymond
2012-03-13 4:16 ` Eric S. Raymond
2012-03-12 21:40 ` tz
2012-03-12 21:27 ` Patrick Maupin
2012-03-12 21:22 ` Patrick Maupin
2012-03-12 21:37 ` Eric S. Raymond
2012-03-12 21:45 ` Patrick Maupin
2012-03-12 22:02 ` Eric S. Raymond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPz3yKfsQVmQYwU7YTVmQZrieGWov2gfEg_wqn18ROP7FqKBPA@mail.gmail.com \
--to=pmaupin@gmail.com \
--cc=esr@thyrsus.com \
--cc=thumbgps-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox