From: John Bradford <john@grabjohn.com>
To: linux-kernel@vger.kernel.org
Subject: Open source hardware
Date: Thu, 16 Jan 2003 17:11:20 +0000 (GMT) [thread overview]
Message-ID: <200301161711.h0GHBKMS001969@darkstar.example.net> (raw)
I've been reading some of the threads about the GPL, and binary-only
drivers, and I'm suprised that nobody has brought up open source
hardware, (or rather, the lack of it).
Open source hardware more or less sidesteps the whole issue of
closed-source drivers - an open source driver would be so easy to
write with all the specifications available that there would be very
little point in writing a closed-source driver.
At the moment there is not very much open source hardware, and what
does exist is generally peripherals, and not things like CPUs, but I
expect this will change soon, mainly because it would be easy to
develop a cheap, and simple CPU that is designed for multi-processor
use from the beginning.
This means that each CPU would be cheap and easy to produce, (simple
design = high yeild from each wafer, and mass production = low cost
per unit). Typical machines would have several orders of magnitude
more processors than those of conventional design, (E.G. 4 to 16 for a
desktop), but they would be far cheaper, because anybody would be free
to fabricate the CPUs.
So, basically, the idea is to design a low-cost,
low-computational-power CPU, which works well in multi-processor
configurations, and make the specification open source. Anybody could
make the processors, and building a machine of a given computational
power would be cheaper using them than using conventional CPUs.
I personally expect to see this within 10 years.
John.
next reply other threads:[~2003-01-16 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 17:11 John Bradford [this message]
2003-01-16 17:36 ` Open source hardware Jeff Garzik
2003-01-16 22:25 ` John Bradford
2003-01-17 16:32 ` Eric W. Biederman
2003-01-16 21:48 ` Herman Oosthuysen
2003-01-17 9:36 ` Remco Post
2003-01-17 10:04 ` John Bradford
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=200301161711.h0GHBKMS001969@darkstar.example.net \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
/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