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

On Iau, 2003-05-01 at 17:53, Jeff Muizelaar wrote:
> Caveats:
> It appears that the patch will break any autoprobe ordering because it no
> longer uses Space.c when compiled into the kernel.

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


  parent reply	other threads:[~2003-05-01 20: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 ` Alan Cox [this message]
2003-05-01 23:29   ` [PATCH 0/4] " Jeff Muizelaar
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=1051817031.21546.23.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®