Andi Kleen 8659c406ad x86: only scan the root bus in early PCI quirks
We found a situation on Linus' machine that the Nvidia timer quirk hit on
a Intel chipset system.  The problem is that the system has a fancy Nvidia
card with an own PCI bridge, and the early-quirks code looking for any
NVidia bridge triggered on it incorrectly.  This didn't lead a boot
failure by luck, but the timer routing code selecting the wrong timer
first and some ugly messages.  It might lead to real problems on other
systems.

I checked all the devices which are currently checked for by early_quirks
and it turns out they are all located in the root bus zero.

So change the early-quirks loop to only scan bus 0.  This incidently also
saves quite some unnecessary scanning work, because early_quirks doesn't
go through all the non root busses.

The graphics card is not on bus 0, so it is not matched anymore.

Signed-off-by: Andi Kleen <ak@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2009-01-09 12:46:22 -08:00
..
2009-01-09 03:39:43 -05:00
2009-01-08 08:31:14 -08:00
2008-12-23 16:29:31 +01:00
2009-01-09 03:39:43 -05:00
2008-10-16 16:53:13 +02:00
2008-12-12 11:08:42 +01:00
2008-12-31 18:07:42 -05:00
2008-07-22 14:35:57 +02:00
2008-12-23 22:37:31 +01:00
2009-01-02 17:46:24 +01:00
2008-07-26 12:00:04 -07:00
2009-01-02 19:24:28 +01:00
2009-01-02 19:03:38 +01:00
2008-10-12 12:37:32 +02:00
2008-12-20 09:15:47 +01:00
2008-12-16 20:36:44 +01:00
2008-10-20 08:52:41 -07:00
2008-07-26 16:31:35 +02:00
2008-07-22 14:35:57 +02:00
2008-10-22 22:55:23 -07:00
2008-12-23 16:30:31 +01:00
2008-07-22 14:35:57 +02:00
2009-01-06 15:59:11 -08:00
2008-10-16 16:53:13 +02:00
2008-10-16 16:53:15 +02:00
2008-07-22 14:35:57 +02:00
2008-10-29 08:02:28 +01:00