> If this is on a shipping BIOS, we might need to figure out some way to
> handle it. I don't remember anything in the ACPI spec that talks
> about issues like this, but maybe we should add something in PCI that
> notices if there's an ACPI device with the same resources and marks
> the PCI device to keep us from moving it or assigning a driver (maybe
> the warning you're seeing already handles the driver part?)
This is, sadly, pretty typical. SMBus devices are often exposed via PCI
even though they're accessed directly via AML. The current behaviour
seems about as good as it gets - we warn the user that this could cause
problems, and they can pass a kernel parameter that allows them to do it
anyway.
--
Matthew Garrett <matthew.garrett@xxxxxxxxxx>
��.n��������+%������w��{.n�����{��-��)�� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
