From: Tony Lee <tony.p.lee@gmail.com>
To: Andre Tomt <andre@tomt.net>
Cc: Tonnerre <tonnerre@thundrix.ch>, Jeff Garzik <jgarzik@pobox.com>,
Andre Bonin <kernel@bonin.ca>,
linux-kernel@vger.kernel.org
Subject: Re: PCI coprocessors
Date: Fri, 17 Sep 2004 09:19:58 -0700 [thread overview]
Message-ID: <470b639704091709191a5fe1d9@mail.gmail.com> (raw)
In-Reply-To: <414AB973.5070408@tomt.net>
On Fri, 17 Sep 2004 12:16:19 +0200, Andre Tomt <andre@tomt.net> wrote:
> Tonnerre wrote:
> > Salut,
> >
> > On Wed, Sep 15, 2004 at 12:01:25PM -0400, Jeff Garzik wrote:
> >
> >>I have long dreamed of being able to add a PCI card to my x86 system, a
> >>PCI card containing a processor (of any type), RAM, and an ethernet
> >>interface. I would use this for routing, or iSCSI, or network offload...
> >
> >
> > Such as the i386 co-computer card for older Macintosh computers? (I
> > can't remember what it was called.)
>
> I've recently seen several ia32 PCI boards, with network, cpu, ram, etc.
> that works in modern PC's. Can't recall any names just now though. Not
> sure if they had any communication with the host over PCI either.
If you can get access to SDK for Broadcom 5704 (570x?) , you have GIGE nic
card with 2 133MHz MIPS CPU, one for TX, onr for RX.
Most of the NIC cards with BCM chip should be < $50.
Maybe enough of us bugging Broadcom, they will open up the SDK.
--
-Tony
Having a lot of fun with Xilinx Virtex Pro II reconfigurable HW + ppc + Linux
prev parent reply other threads:[~2004-09-17 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 12:55 PCI coprocessors Andre Bonin
2004-09-15 12:30 ` Alan Cox
2004-09-15 13:44 ` Matti Aarnio
2004-09-15 13:45 ` Richard B. Johnson
2004-09-15 14:55 ` Tomasz Rola
2004-09-15 15:15 ` Andre Bonin
2004-09-15 16:49 ` Tonnerre
2004-09-16 0:12 ` Tomasz Rola
2004-09-15 16:01 ` Jeff Garzik
2004-09-15 22:39 ` Tonnerre
2004-09-17 10:16 ` Andre Tomt
2004-09-17 16:19 ` Tony Lee [this message]
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=470b639704091709191a5fe1d9@mail.gmail.com \
--to=tony.p.lee@gmail.com \
--cc=andre@tomt.net \
--cc=jgarzik@pobox.com \
--cc=kernel@bonin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=tonnerre@thundrix.ch \
/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