Re: PCI bridge range sizing bug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




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).

So I'd suggest that at least initially, we could/should just make it a 
decision based on a command line flag like the "pci=assign-busses" thing 
is now (which forces bus *numbers* to be re-assigned regardless of how 
they were assigned by the firmware, not the actual resources).

Because realistically, I don't think we'll see any common PC platform that 
actually needs it. Simply because I seriously doubt Windows reassignes bus 
resources either.

Ivan, want to add some way to force that allocation (something like 
"pci=assign-bus-resources")

		Linus
-
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]
  Powered by Linux