lkml.org 
[lkml]   [2007]   [Apr]   [21]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateSat, 21 Apr 2007 01:31:38 -0400
FromRik van Riel <>
SubjectRe: PCI bridge range sizing bug
Jesse Barnes wrote:
> On Friday, April 20, 2007 11:28 am Linus Torvalds wrote:
>> On Fri, 20 Apr 2007, Jesse Barnes wrote:
>>> Sounds good, hopefully reassigning the bridge resources won't cause
>>> too much trouble.  Do you have time to hack this up?  If not, I
>>> could give it a try, as long as ajax is willing to test...
>> Actually, I would suggest we not do it automatically (because the
>> need for it is just so low, and the downsides are potentially huge -
>> there are just too many resources that are "hidden" from us through
>> ACPI tricks and having hardware that doesn't actually expose their
>> PCI resources fully through the normal PCI resource setup).
> 
> Yeah, that's probably prudent.  OTOH we should probably let the user 
> know in no uncertain terms that some of the stuff behind one of their 
> bridges will be inaccessible.

Something like that would have made it a lot more obvious
why my Matrox PCIe x1 video card will not work in my Dell
9150, while a PCI video card does work.

The PCI video card directly sits on the bus, and gets its
resources assigned by the BIOS.

The PCIe video card turned out to be a PCIe to AGP bridge,
and the BIOS did not assign the needed PCI resources, making
the system crash when I started X.

X seemed to have some trouble reading the ROM, too...

-- 
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is.  Each group
calls the other unpatriotic.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-04-21 07:35    [from the cache]
©2003-2008