From: "M.H.VanLeeuwen" <vanl@megsinet.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: mflt1@micrologica.com.hk, ambx1@neo.rr.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ISAPNP BUG: 2.4.65 ne2000 driver w. isapnp not working
Date: Sun, 23 Mar 2003 13:26:43 -0600 [thread overview]
Message-ID: <3E7E0A73.3D00B9CB@megsinet.net> (raw)
In-Reply-To: <1048443865.10727.36.camel@irongate.swansea.linux.org.uk>
Alan Cox wrote:
>
> On Sun, 2003-03-23 at 16:26, M.H.VanLeeuwen wrote:
> > NE2k ISAPNP broke around 2.5.64, again. There are 2 parts to the attached
> > patch, one to move the NIC initialization earlier in the boot sequence
> > and the second is a HACK to get ne2k to work when compiled into the
> > kernel, I've never tried NE2k as a module...
> >
> > 1. The level of isapnp_init was moved to after apci. Since it is now
> > after net_dev_init, ISA PNP NICs fail to initialized at boot.
> >
> > This fix allows ISA PNP NIC cards to work during net_dev_init, and still
> > leaves isapnp_init after apci_init.
>
> We must initialise ACPI before ISAPnP because we need PCI and ACPI to
> know what system resources we must not hit. How about moving the
> net_dev_init to later ?
Here is the ordering of initcall from System.map file w/ my change.
I take it that you want isapnp_init after pci*_init also, or is it sufficient
like it is, after the acpi*_init?
c0410f30 t __initcall_init_bio
c0410f34 t __initcall_acpi_init
c0410f38 t __initcall_acpi_ec_init
c0410f3c t __initcall_acpi_pci_root_init
c0410f40 t __initcall_acpi_pci_link_init
c0410f44 t __initcall_acpi_power_init
c0410f48 t __initcall_acpi_system_init
c0410f4c t __initcall_acpi_event_init
c0410f50 t __initcall_acpi_scan_init
c0410f54 t __initcall_pnp_init
c0410f58 t __initcall_pnp_system_init
c0410f5c t __initcall_isapnp_init <<<<<< patch moved it here <<<
c0410f60 t __initcall_device_init
c0410f64 t __initcall_deadline_slab_setup
c0410f68 t __initcall_pci_acpi_init
c0410f6c t __initcall_pci_legacy_init
c0410f70 t __initcall_pcibios_irq_init
c0410f74 t __initcall_pcibios_init
c0410f78 t __initcall_net_dev_init
c0410f7c t __initcall_init_8259A_devicefs
Or is this not the place to see initcall ordering?
Looking into moving net_dev_init to later...
Martin
next prev parent reply other threads:[~2003-03-23 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 16:26 M.H.VanLeeuwen
2003-03-23 17:57 ` Michael Frank
2003-03-23 18:41 ` M.H.VanLeeuwen
2003-03-23 18:24 ` Alan Cox
2003-03-23 19:26 ` M.H.VanLeeuwen [this message]
2003-03-23 20:40 ` Alan Cox
2003-03-24 0:24 ` Michael Frank
[not found] ` <200303241203.01814.mflt1@micrologica.com.hk>
[not found] ` <3E81A494.FF16EBCF@megsinet.net>
2003-03-26 14:20 ` Resolved: " Michael Frank
-- strict thread matches above, loose matches on Subject: below --
2003-03-23 6:01 Michael Frank
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=3E7E0A73.3D00B9CB@megsinet.net \
--to=vanl@megsinet.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ambx1@neo.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mflt1@micrologica.com.hk \
/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®