Messages in this thread | | | From | Bjorn Helgaas <> | Date | Thu, 20 Mar 2014 14:48:30 -0600 | Subject | Re: Info: mapping multiple BARs. Your kernel is fine. |
| |
On Thu, Mar 20, 2014 at 2:55 PM, Rafael J. Wysocki <rjw@rjwysocki.net> wrote: > On Thursday, March 20, 2014 10:45:52 AM Bjorn Helgaas wrote: >> The purpose of system.c is indeed to prevent resources from being >> allocated to other devices. This is really a question for Rafael, but >> in my opinion this function (reserving resources of PNP/ACPI devices >> to prevent their allocation to other devices) should be done for *all* >> PNP and ACPI devices, not just the PNP0C01/PNP0C02 devices handled by >> system.c. >> >> So I think the best solution would be to move that into the ACPI core >> somehow so it happens for all devices. > > Well, I think you got to the bottom of this, but that's something we can > do long-term. Still, we need to find a short-term solution for the > particular issue at hand.
Right. Even if we had this long-term solution, we'd still have Stephane's current problem, because the PNP0C02 _CRS is still wrong.
We do have a drivers/pnp/quirks.c where we could conceivably adjust the PNP resource if we found the matching PCI device and MCHBAR. That should solve Stephane's problem even with the current drivers/pnp/system.c.
Bjorn
| |