Re: Initialization order of PCI devices

From: Richard B. Johnson (root@chaos.analogic.com)
Date: Sun Jun 11 2000 - 21:45:43 EST


On Sun, 11 Jun 2000, Riley Williams wrote:

>
[SNIPPED...]
 
> What I would like to see is some means of booting an NFSroot box
> and telling the kernel "The boot net interface is always the
> Tulip one, so use it at boot time as eth0".
>
> As far as I know, this isn't possible if there's two or more
> different types of interface present.
>
> Best wishes from Riley.
>

A simple program shows the PCI devices in their incremental search
order:

Device Vendor Type
   0 Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge
   1 Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge
   4 Intel Corporation 82371AB PIIX4 ISA
   9 S3 Inc. 86c968 [Vision 968 VRAM] rev 0 IRQ 12
  11 3Com Corporation 3c905B 100BaseTX [Cyclone] IRQ 10
  12 BusLogic BT-946C (BA80C30), [MultiMaster 10] IRQ 11

This program didn't use /proc, but it could have. Using /proc/pci, it's
trivial.

If I had two network devices on this system, they would have different
device numbers.

The drivers could be modified to accept DEV=11,15,22 parameters to
define the initialization order.

Cheers,
Dick Johnson

Penguin : Linux version 2.3.36 on an i686 machine (400.59 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:24 EST