This was necessary because the PCI driver (scan/enumeration code) was using
these same config calls that was being fixed up.  (A chicken and egg issue?)

This should still not be necessary... Before scanning a bus, the PCI code
will properly set first_busno, thus the config access methods will work.

The only problem I spotted in 2.4 (and afaik, that is fixed in 2.6) is
that when P2P bridges are moved around, we could end up with a temporary
wrong state where 2 of these on a given bus segment would try to decode
the same bus numbers, thus screwing up probe. This is why I added a
skew value of 0x10 between each host on some machines.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/