lkml.org 
[lkml]   [2003]   [Mar]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ISAPNP BUG: 2.4.65 ne2000 driver w. isapnp not working
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:34    [W:0.171 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site