From: "Kevin D. Kissell" <kevink@mips.com>
To: "David Milburn" <dmilburn@redhat.com>, <linux-mips@oss.sgi.com>
Subject: Re: PCI ethernet cards
Date: Wed, 27 Mar 2002 09:26:50 +0100 [thread overview]
Message-ID: <002301c1d569$4af46ea0$0deca8c0@Ulysses> (raw)
In-Reply-To: 3CA10449.F0088B95@redhat.com
> Can anyone recommend some PCI 100 Mbit ethernet cards/drivers
> that work well with the 2.4 linux-mips kernel?
At MIPS, we use AMD PCnet32 cards pretty exclusively,
and with good success under both 2.2 and 2.4. For 2.2,
we did a pretty thorough reworking of the driver to deal with
MIPS endianness and (especially) cache issues, but I believe
we use the 2.4 driver "out of the box". YMMV, of course.
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: David Milburn <dmilburn@redhat.com>, linux-mips@oss.sgi.com
Subject: Re: PCI ethernet cards
Date: Wed, 27 Mar 2002 09:26:50 +0100 [thread overview]
Message-ID: <002301c1d569$4af46ea0$0deca8c0@Ulysses> (raw)
Message-ID: <20020327082650.UbwPpFgjsGlLEUC9JLD3-GBWoopoxFZ3-gRii10IsK4@z> (raw)
In-Reply-To: 3CA10449.F0088B95@redhat.com
> Can anyone recommend some PCI 100 Mbit ethernet cards/drivers
> that work well with the 2.4 linux-mips kernel?
At MIPS, we use AMD PCnet32 cards pretty exclusively,
and with good success under both 2.2 and 2.4. For 2.2,
we did a pretty thorough reworking of the driver to deal with
MIPS endianness and (especially) cache issues, but I believe
we use the 2.4 driver "out of the box". YMMV, of course.
Kevin K.
next prev parent reply other threads:[~2002-03-27 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-26 23:29 PCI ethernet cards David Milburn
2002-03-27 7:42 ` Kevin Paul Herbert
2002-03-27 8:26 ` Kevin D. Kissell [this message]
2002-03-27 8:26 ` Kevin D. Kissell
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='002301c1d569$4af46ea0$0deca8c0@Ulysses' \
--to=kevink@mips.com \
--cc=dmilburn@redhat.com \
--cc=linux-mips@oss.sgi.com \
/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.