* [PATCH] x86/PCI: ignore Consumer/Producer bit in ACPI window descriptions
@ 2010-04-06 19:24 Bjorn Helgaas
2010-04-08 16:25 ` Jesse Barnes
0 siblings, 1 reply; 2+ messages in thread
From: Bjorn Helgaas @ 2010-04-06 19:24 UTC (permalink / raw)
To: Jesse Barnes; +Cc: linux-pci, linux-kernel, Thomas Renninger
ACPI Address Space Descriptors (used in _CRS) have a Consumer/Producer
bit that is supposed to distinguish regions that are consumed directly
by a device from those that are forwarded ("produced") by a bridge.
But BIOSes have apparently not used this consistently, and Windows
seems to ignore it, so I think Linux should ignore it as well.
I can't point to any of these supposed broken BIOSes, but since we
now rely on _CRS by default, I think it's safer to ignore this bit
from the start.
Here are details of my experiments with how Windows handles it:
https://bugzilla.kernel.org/show_bug.cgi?id=15701
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
---
arch/x86/pci/acpi.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/arch/x86/pci/acpi.c b/arch/x86/pci/acpi.c
index c7b1ebf..334153c 100644
--- a/arch/x86/pci/acpi.c
+++ b/arch/x86/pci/acpi.c
@@ -71,8 +71,7 @@ resource_to_addr(struct acpi_resource *resource,
if (ACPI_SUCCESS(status) &&
(addr->resource_type == ACPI_MEMORY_RANGE ||
addr->resource_type == ACPI_IO_RANGE) &&
- addr->address_length > 0 &&
- addr->producer_consumer == ACPI_PRODUCER) {
+ addr->address_length > 0) {
return AE_OK;
}
return AE_ERROR;
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] x86/PCI: ignore Consumer/Producer bit in ACPI window descriptions
2010-04-06 19:24 [PATCH] x86/PCI: ignore Consumer/Producer bit in ACPI window descriptions Bjorn Helgaas
@ 2010-04-08 16:25 ` Jesse Barnes
0 siblings, 0 replies; 2+ messages in thread
From: Jesse Barnes @ 2010-04-08 16:25 UTC (permalink / raw)
To: Bjorn Helgaas; +Cc: linux-pci, linux-kernel, Thomas Renninger
On Tue, 06 Apr 2010 13:24:08 -0600
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>
> ACPI Address Space Descriptors (used in _CRS) have a Consumer/Producer
> bit that is supposed to distinguish regions that are consumed directly
> by a device from those that are forwarded ("produced") by a bridge.
> But BIOSes have apparently not used this consistently, and Windows
> seems to ignore it, so I think Linux should ignore it as well.
>
> I can't point to any of these supposed broken BIOSes, but since we
> now rely on _CRS by default, I think it's safer to ignore this bit
> from the start.
>
> Here are details of my experiments with how Windows handles it:
> https://bugzilla.kernel.org/show_bug.cgi?id=15701
>
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> ---
Applied to my for-linus branch, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-04-08 16:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-06 19:24 [PATCH] x86/PCI: ignore Consumer/Producer bit in ACPI window descriptions Bjorn Helgaas
2010-04-08 16:25 ` Jesse Barnes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).