> ok, in other words:
> 2.6.16: end result: direct access; if direct doesn't work: pcibios
> 2.6.17: end result: pci bios (only direct if pcibios fails! )
> 2.6.17+patch: end result: direct access; if direct doesn't work: pcibios
> => net result is the same, but less code is executed, order is clear always.
Makes sense. PCI BIOS access is totally obsolete and should only be used
when everything else fails.
> btw. it's commit 92c05fc1a32e5ccef5e0e8201f32dcdab041524c
> ([PATCH] PCI: Give PCI config access initialization a defined ordering)
> that broke things on those laptops. cc'ing Andi...
It could have broken before where the order was essentially random.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
