From: Jeff Garzik <jgarzik@pobox.com>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Open source hardware
Date: Thu, 16 Jan 2003 12:36:34 -0500 [thread overview]
Message-ID: <20030116173634.GA16376@gtf.org> (raw)
In-Reply-To: <200301161711.h0GHBKMS001969@darkstar.example.net>
On Thu, Jan 16, 2003 at 05:11:20PM +0000, John Bradford wrote:
> 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).
[...]
> 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.
You're behind the times :)
http://www.opencores.org/
next prev parent reply other threads:[~2003-01-16 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 17:11 Open source hardware John Bradford
2003-01-16 17:36 ` Jeff Garzik [this message]
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=20030116173634.GA16376@gtf.org \
--to=jgarzik@pobox.com \
--cc=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