Any chance of a fix for this before 2.6.34 is released? Cheers, Peter On Wed, 2010-04-21 at 08:54 -0700, Jesse Barnes wrote: > On Tue, 20 Apr 2010 23:06:09 -0700 > Yinghai <yinghai.lu@xxxxxxxxxx> wrote: > > after several times retry, mmio ranges get assigned, but io port range can be allocated enough range. it needs 16k, > > but under 05:01.0 to 08:00.0 and 09:04.0 orginal io port from BIOS allocation get lost. > > > > wonder be good, if We can restore it for such case. > > > > current may have to disable bridge resizing feature by default. > > > > can you send out > > lspci -vvxxx > > lspci -tv > > Since we don't really know which devices will be in use until drivers > load (and not even then if they're userspace drivers), it might be best > to put off the reassignment until a PCI driver expresses an interest in > the range. > > At least, it seems like that would be closer to the ideal approach than > trying to reassign everything at boot, potentially making devices that > don't matter get resources and leaving important devices disabled. > -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
