From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Choosing an Ethernet controller...
Date: Mon, 18 Jan 1999 20:26:00 +0100 [thread overview]
Message-ID: <19990118202600.009236@mail.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990118095104.18478A-100000@persephone.cs.nmt.edu>
I know this is a little bit out-of-topic, but I'm sure someone on this
list can answer and I didn't really know how to actually ask this...
For an embedded developement, I have to choose among 3 different PCI
ethernet controllers. A DEC/Intel 21143 (Tulip), an AMD79C971 (PCNet32)
or a SMC83C171 (Epic100).
The processor will not be a PPC but a StrongARM. (we proposed a PPC, but
the client wanted a StrongARM).
All three seems to be supported by Linux, I will use a 2.0.x kernel at
first, on a StrongARM, but we plan to move to 2.2 once it's stable enough.
Are there any known problems with one of those chips ? Is someone aware
of any specific problem with one of those beasts or it's linux driver ?
Which one would you choose ?
Thanks !
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
prev parent reply other threads:[~1999-01-18 19:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.96.990114142507.7102A-200000@persephone.cs.nmt.edu>
1999-01-14 22:35 ` new irq.c Geert Uytterhoeven
1999-01-18 1:19 ` MCLK=100 breaks PowerBook Benjamin Herrenschmidt
1999-01-18 9:00 ` Geert Uytterhoeven
1999-01-18 16:51 ` Cort Dougan
1999-01-18 17:04 ` Geert Uytterhoeven
1999-01-19 0:47 ` Paul Mackerras
1999-01-19 12:35 ` Geert Uytterhoeven
1999-01-18 19:26 ` Benjamin Herrenschmidt [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=19990118202600.009236@mail.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.