From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
Dave Airlie <airlied@csn.ul.ie>,
SGI MIPS list <linux-mips@oss.sgi.com>,
Debian MIPS list <debian-mips@lists.debian.org>,
engel@unix-ag.org
Subject: Re: [long] Lance on DS5k/200
Date: Tue, 31 Jul 2001 02:32:45 +0200 [thread overview]
Message-ID: <20010731023245.A6371@solo.franken.de> (raw)
In-Reply-To: <20010731002421.A19713@lug-owl.de>; from jbglaw@lug-owl.de on Tue, Jul 31, 2001 at 12:24:21AM +0200
On Tue, Jul 31, 2001 at 12:24:21AM +0200, Jan-Benedict Glaw wrote:
> Of course. I wouldn't even *try* to do sth other. In fact, I'm looking
> around for various specs of various implementations (as seen from
> the bus) of the LANCE chip to see if I could manage the job to
> unify them all together:
> ./drivers/net/pcnet32.c none mentioned
even if it's based on the lance design from AMD (and it support a lance
compatible mode), you won't be able to unify this driver with other lance
drivers since the driver uses the 32bit mode of the pcnet32 chip familiy
79C97[0-8]).
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ Alexander Viro on linux-kernel ]
next prev parent reply other threads:[~2001-07-31 0:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-28 19:41 [long] Lance on DS5k/200 Jan-Benedict Glaw
2001-07-29 0:14 ` Florian Lohoff
2001-07-30 20:04 ` Maciej W. Rozycki
2001-07-29 13:16 ` Dave Airlie
2001-07-29 13:16 ` Dave Airlie
2001-07-30 20:06 ` Maciej W. Rozycki
2001-07-30 22:24 ` Jan-Benedict Glaw
2001-07-30 22:45 ` Maciej W. Rozycki
2001-07-30 22:45 ` Jan-Benedict Glaw
2001-07-29 21:26 ` Alan Cox
2001-07-29 21:26 ` Alan Cox
2001-07-30 23:00 ` Maciej W. Rozycki
2001-07-31 0:32 ` Thomas Bogendoerfer [this message]
2001-07-31 7:08 ` Geert Uytterhoeven
2001-08-02 13:45 ` Dave Airlie
2001-08-02 13:45 ` Dave Airlie
2001-07-31 7:03 ` Geert Uytterhoeven
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=20010731023245.A6371@solo.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=airlied@csn.ul.ie \
--cc=debian-mips@lists.debian.org \
--cc=engel@unix-ag.org \
--cc=jbglaw@lug-owl.de \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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