On 20 Jul 00 at 9:56, Dennis wrote:
> None of this blabber of yours solves the problem, so why waste everyone's
> time? Explaining why its broken is kind of like your mechanic telling you
> why your brakes sqeak. I dont care why they sqeak, i want them to stop
> sqeaking.
>
> What code needs to be changed to fix it? Im sure Im not the only one who'd
> like to know.
I have patch for 2.4.x which adds 'pciorder=' option to kernel, so
I can swap my two bttv interfaces with 'pciorder=0:0b.0,0:0a.0' or
'pciorder=0:0a.0,0:0b.0'.
Unfortunately, you have two choices:
a) Either patch can order all devices (even different types, so
you can have tulip eth0, 3com eth1 and again tulip eth2; some drivers
needs tweaking, as all devices appear as `hotplug' to drivers with
this patch), but ACPI does not work,
b) or you can order only devices driven by one driver and ordering
between different drivers is derived from link order (this one is ACPI
compatible, but you cannot swap 3Com with Tulip...) (2.2.x can support
only this way; some non-hotplug drivers does not support this and always
search for devices in chip type order, not in bus order).
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu
