Take the whole PCI bus range into account when scanning PCI bridges.
commit8b5915b08dda13ffe1f70f00322dcc34ce161904
authorLinus Torvalds <torvalds@ppc970.osdl.org>
Thu, 14 Oct 2004 04:03:12 +0000 (13 21:03 -0700)
committerLinus Torvalds <torvalds@ppc970.osdl.org>
Thu, 14 Oct 2004 04:03:12 +0000 (13 21:03 -0700)
tree81c0fbb962ab16bdedbe6eb9db34c57d797c1c56
parent538ce05c0ef4055cf29a92a4abcdf139d180a0f9
Take the whole PCI bus range into account when scanning PCI bridges.

A bridge that has been set up by firmware to cover multiple PCI
buses but doesn't actually have anything connected behind some of
them caused us to use the incorrect maxmimum bus number span when
scanning the bridge chip.

Problem reported by Tim Saunders, with Russell King suggesting
the fix.
drivers/pci/probe.c