From: Pete Zaitcev <zaitcev@redhat.com>
To: jbglaw@lug-owl.de, linux-kernel@vger.kernel.org
Subject: Re: LANCE ethernet chip - ~24 drivers
Date: Mon, 30 Jul 2001 20:44:01 -0400 [thread overview]
Message-ID: <200107310044.f6V0i1s04417@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.996536700.4319.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.996536700.4319.linux-kernel2news@redhat.com>
> ./drivers/net/sunlance.c NCR92c990
> `-> Father of declance.c as I think
It handles 79c90, but also includes support for ledma,
lebuffer, and Lance-fixed-with-PAL. Hardly a target for merge.
> ./drivers/net/sunhme.c none mentioned
> `-> *some* cards seem to be compatible?!
Nope, not even close. Make it 23 Lance drivers.
> ./drivers/net/sunqu.c "looks like LANCE"
QE is a quad of some Lance derivatives, plus a bus interface
for DMA which is not compatible with ledma. It is sufficiently
unusual for Solaris to have separate drivers for le and qe.
> ./drivers/net/sun3lance.c none mentioned,
> but adopted from sunlance.c
Yes, they are basically the same. Dunno why sun3 people split it.
> However - having
> more than 20 drivers for one kind of device sucks a lot.
Not really, as long as they are maintained.
> I think, it will be a 2.5.x thing to
> re-unify them again (at lease, write a central implementation
> for the chip and let bus specific drivers use it). Just the
> same words are to be said for the Zilog8530 serial chip.
Large number of them is going to die fromm bitrot naturally,
so I do not see a major problem. For instance, sunle is going
to disappear in 5..10 years, as old machines break down.
-- Pete
next parent reply other threads:[~2001-07-31 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.996536700.4319.linux-kernel2news@redhat.com>
2001-07-31 0:44 ` Pete Zaitcev [this message]
2001-07-31 16:58 LANCE ethernet chip - ~24 drivers Rick Hohensee
2001-07-31 18:14 ` Horst von Brand
2001-08-01 8:39 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2001-07-30 23:42 Jan-Benedict Glaw
2001-08-01 21:55 ` Jeff Garzik
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=200107310044.f6V0i1s04417@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
/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