linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Muizelaar <muizelaar@rogers.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] NE2000 driver updates
Date: Fri, 02 May 2003 11:57:26 -0400	[thread overview]
Message-ID: <3EB29566.4000903@pobox.com> (raw)
In-Reply-To: <1051884070.23249.4.camel@dhcp22.swansea.linux.org.uk>

Alan Cox wrote:
> On Gwe, 2003-05-02 at 00:29, Jeff Muizelaar wrote:
> 
>>Are we stuck with Space.c forever? Anyone have any plans for replacing 
>>it with something more driver-model friendly?
> 
> 
> Is it worth the effort. Why not just let the old isa stuff live out its
> life in peace ?


I'm glad you asked.  :)

For the major families of ISA net drivers, I am craving massive 
consolidation.  People continue to use this stuff in embedded systems 
and simulators, long past when the original cards disappear into the 
ether, too.  Considering that operations are inevitably IO bound, I am 
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.

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]

Did I mention that a GIGE ne2000 card exists?

	Jeff



[1] of course, with decent, free MAC and PHY cores at www.opencores.org, 
maybe we can convince hardware makers to use a better design.  </plug>


  reply	other threads:[~2003-05-02 15:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 16:53 [PATCH 0/4] NE2000 driver updates 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 [this message]
2003-05-02 15:24         ` Alan Cox
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=3EB29566.4000903@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).