Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Carsten Langgaard <carstenl@mips.com>
Cc: Michael Shmulevich <michaels@jungo.com>,
	"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: MIPS/linux compatible PCI network cards
Date: Thu, 25 Jan 2001 23:43:03 -0800	[thread overview]
Message-ID: <20010125234303.G3512@bacchus.dhis.org> (raw)
In-Reply-To: <3A712A52.FAC574F1@mips.com>; from carstenl@mips.com on Fri, Jan 26, 2001 at 08:42:10AM +0100

On Fri, Jan 26, 2001 at 08:42:10AM +0100, Carsten Langgaard wrote:

> 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.

The biggest grief I had was that about every embedded system I ever had
uses violates the common standard for what is supposed to be in the
EEPROMs of the Tulip or simply doesn't have one at all ...

  Ralf

  reply	other threads:[~2001-01-26  7:46 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 [this message]
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
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=20010125234303.G3512@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=carstenl@mips.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