public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: jgarzik@pobox.com (Jeff Garzik)
Cc: Herman@wirelessnetworksinc.com, linux-kernel@vger.kernel.org
Subject: Re: Open source hardware
Date: Thu, 16 Jan 2003 22:25:00 +0000 (GMT)	[thread overview]
Message-ID: <200301162225.h0GMP0YI003249@darkstar.example.net> (raw)
In-Reply-To: <20030116173634.GA16376@gtf.org> from "Jeff Garzik" at Jan 16, 2003 12:36:34 PM

> > 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/

Interesting - I'd only seen open source CPU projects which were at the
planning stage.

It seems that most of the components necessary to build a usable
machine are at least well-advanced, although most of the non-CPU parts
are based around the WISHBONE interface, whereare most of the CPUs are
not, so maybe the goal is further away than it first appears, but
still, progress is being made.

Do you know of anybody who has actually made a prototype board from
any of these CPU designs?  Is my idea of running a lot of simple CPUs
together fundamentally flawed, or is it possible to overcome the
inefficiencies of SMP, if the CPUs are designed for it from the ground
up?

To be honest I am really begining to get bored with i386-based
systems, and I'm hoping to move away from them entirely at the
earliest opportunity.  Hopefully I'll be building my next machine
around an UltraSPARC, but I've really been a bit too busy with other
projects lately...

John.

  reply	other threads:[~2003-01-16 22:16 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
2003-01-16 22:25   ` John Bradford [this message]
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=200301162225.h0GMP0YI003249@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=Herman@wirelessnetworksinc.com \
    --cc=jgarzik@pobox.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