On Thu, Jun 27, 2013 at 04:54:05PM +0300, Mika Westerberg wrote:
> I think that we can get this working so that we add a new flag to struct
> pci_dev, something like 'no_additional_hotplug_bus_space' and in this quirk
> set that.
>
> Then in __pci_bus_size_bridges() we do:
>
> pci_bridge_check_ranges(bus);
> if (bus->self->is_hotplug_bridge &&
> !bus->self->no_additional_hotplug_bus_space) {
> additional_io_size = pci_hotplug_io_size;
> additional_mem_size = pci_hotplug_mem_size;
> }
>
> This should prevent the problem this patch was trying to solve. Does that
> work for you?
Forget about that -- It looks like these messages are harmless:
pcieport 0000:0a:05.0: BAR 8: can't assign mem (size 0x200000)
pcieport 0000:0a:05.0: BAR 9: can't assign mem pref (size 0x200000)
It just means that we tried to allocate the resource but failed because the
bridge has that window closed, if I got it right. If user doesn't want to
see those, he/she can always pass 'pci=hpmensize=0,hpiosize=0' in the
kernel command line.
With pcibios_resource_survey_bus() fix, looks like this quirk is not needed
at all.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
