From: Carsten Langgaard <carstenl@mips.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
Michael Shmulevich <michaels@jungo.com>,
linux-mips@oss.sgi.com
Subject: Re: MIPS/linux compatible PCI network cards
Date: Fri, 26 Jan 2001 12:47:26 +0100 [thread overview]
Message-ID: <3A7163CE.8EDE5CF7@mips.com> (raw)
In-Reply-To: 019b01c0878d$8ac9e6c0$0deca8c0@Ulysses
"Kevin D. Kissell" wrote:
> > > > Hello all,
> > > >
> > > > I would like to ask if someone knows some more or less widely
> available
> > > > PCI network card that is compatible with MIPS/Linux.
> > > >
> > > > I have heard of Tulip and AMD's PCnet. I wonder if you heard of
> others.
> > >
> > > These all have already been used with Linux/MIPS. I don't have any
> reports
> > > on the current status of these drivers. If they don't work they should
> > > be reasonably easy to fix.
> >
> > The tulip driver worked fine at least in the past. The AMD PCnet driver
> works
> > just fine, we are using it on our reference boards.
>
> Note, however, that the Tulip driver that was part of the
> standard 2.2/2.3 repository at oss.sgi.com was both
> downrev with regard to the author's own web site and
> subobtimal if not outright buggy in it's cache management.
> The AMD PCnet driver as we found it was clean and efficient
> but had no MIPS cache hooks. I had to put those in.
> So unless Ralf or someone at SGI that the versions
> on oss.sgi.com are the versions I cleaned up for MIPS,
> I would recommend pulling them off the MIPS site.
>
The AMD PCnet driver should be OK in the CVS from oss.sgi.com
>
> Regards,
>
> Kevin K.
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2001-01-26 11:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 22:06 MIPS/linux compatible PCI network cards Michael Shmulevich
2001-01-25 22:16 ` Ralf Baechle
2001-01-26 7:42 ` Carsten Langgaard
2001-01-26 7:43 ` Ralf Baechle
2001-01-26 11:45 ` Kevin D. Kissell
2001-01-26 11:45 ` Kevin D. Kissell
2001-01-26 11:47 ` Carsten Langgaard [this message]
2001-01-26 11:49 ` Carsten Langgaard
2001-01-26 21:00 ` Ralf Baechle
2001-01-26 21:00 ` Ralf Baechle
2001-01-25 22:22 ` Pete Popov
2001-01-25 22:29 ` Ralf Baechle
2001-01-26 7:56 ` Michael Shmulevich
2001-01-26 7:56 ` Michael Shmulevich
2001-01-26 18:17 ` Pete Popov
2001-01-27 8:58 ` Michael Shmulevich
2001-01-27 21:31 ` Pete Popov
2001-01-28 10:20 ` Michael Shmulevich
2001-01-27 19:22 ` Ralf Baechle
2001-01-28 10:11 ` Michael Shmulevich
2001-01-26 19:53 ` Jun Sun
2001-01-27 19:25 ` Ralf Baechle
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=3A7163CE.8EDE5CF7@mips.com \
--to=carstenl@mips.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=michaels@jungo.com \
--cc=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox