From: Jun Sun <jsun@mvista.com>
To: Michael Shmulevich <michaels@jungo.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: MIPS/linux compatible PCI network cards
Date: Fri, 26 Jan 2001 11:53:10 -0800 [thread overview]
Message-ID: <20010126115310.D9325@mvista.com> (raw)
In-Reply-To: <3A70A356.F3CA71F1@jungo.com>; from michaels@jungo.com on Fri, Jan 26, 2001 at 12:06:14AM +0200
On Fri, Jan 26, 2001 at 12:06:14AM +0200, Michael Shmulevich 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.
>
> Thanks in advance,
> Sorry if this mail bothered you...
>
Intel eepro100 works on mips too. What I had to modify is to
1) take care of the non-standard EEPROM
2) set rx_copybreak to 1518 to avoid some cache problem.
3) remove a buggy cpu_to_le32() coversion
I sent a patch to the author. Hopefully next release it will be
ready for MIPS.
Jun
next prev parent reply other threads:[~2001-01-26 19:54 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
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 [this message]
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=20010126115310.D9325@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=michaels@jungo.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