All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Muizelaar <muizelaar@rogers.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] NE2000 driver updates
Date: Thu, 01 May 2003 19:29:48 -0400	[thread overview]
Message-ID: <3EB1ADEC.6080007@rogers.com> (raw)
In-Reply-To: <1051817031.21546.23.camel@dhcp22.swansea.linux.org.uk>

Alan Cox wrote:

>
>The ne2000 ordering with the other ISA stuff in space.c is really
>sensitive for older systems. If you get ne2k too early it breaks some
>other cards if it autoprobes, if you get it too late it lets other
>stuff crash the box.
>
>So you might want to keep to Space.c for non pnp stuff if non modular
>  
>
Yeah, patches 1 and 2 do just this.

Are we stuck with Space.c forever? Anyone have any plans for replacing 
it with something more driver-model friendly?

-Jeff


  reply	other threads:[~2003-05-01 23:17 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 [this message]
2003-05-02 14:01     ` Alan Cox
2003-05-02 15:57       ` Jeff Garzik
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=3EB1ADEC.6080007@rogers.com \
    --to=muizelaar@rogers.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.