From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Jeff Muizelaar <muizelaar@rogers.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] NE2000 driver updates
Date: 02 May 2003 16:24:35 +0100 [thread overview]
Message-ID: <1051889074.23255.9.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3EB29566.4000903@pobox.com>
On Gwe, 2003-05-02 at 16:57, Jeff Garzik wrote:
> even willing to spend a few (admittedly costly) extra cycles chasing
> some additional function pointer de-refs, if we could massively shrink
> the size and number of NE2000/lance/82596 drivers out there.
Well the 8390 (ne2000 etc) has been abstracted cleanly for a very long
time indeed. 825xx is a pig because they chip variants are all subtly
and evilly different.
> I guarantee these drivers are gonna be with us for many years to come,
> and designers wanting to bang out a quick-and-easy MAC will create Yet
> Another NE2000 Clone.[1]
They seem to be cloning tulip nowdays
> Did I mention that a GIGE ne2000 card exists?
I've got a 100Mbit one.
Alan
next prev parent reply other threads:[~2003-05-02 16:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 16:53 Jeff Muizelaar
2003-05-01 16:58 ` [PATCH 1/4] " Jeff Muizelaar
2003-05-01 16:59 ` [PATCH 2/4] " Jeff Muizelaar
2003-05-01 16:59 ` [PATCH 3/4] " Jeff Muizelaar
2003-05-01 17:08 ` Jeff Muizelaar
2003-05-01 17:47 ` [PATCH 4/4] " Jeff Muizelaar
2003-05-01 19:23 ` [PATCH 0/4] " Alan Cox
2003-05-01 23:29 ` Jeff Muizelaar
2003-05-02 14:01 ` Alan Cox
2003-05-02 15:57 ` Jeff Garzik
2003-05-02 15:24 ` Alan Cox [this message]
2003-05-02 16:29 ` Riley Williams
2003-05-14 2:01 ` Jeff Muizelaar
2003-05-14 21:51 ` Adam Belay
2003-05-15 3:01 ` Jeff Muizelaar
[not found] <BKEGKPICNAKILKJKMHCACEOMCPAA.Riley@Williams.Name>
2003-05-14 11:02 ` Alan Cox
2003-05-14 23:11 ` Jeff Muizelaar
2003-05-14 22:46 ` Jeff Muizelaar
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=1051889074.23255.9.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muizelaar@rogers.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
all inboxes | Powered by JetHome®