Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1167330 > unrolled thread
| Started by | Bjorn Helgaas <bhelgaas@google.com> |
|---|---|
| First post | 2015-06-18 01:10 +0200 |
| Last post | 2015-06-18 01:10 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 0/2] x86/PCI: enable pci=use_crs for more machines Bjorn Helgaas <bhelgaas@google.com> - 2015-06-18 01:10 +0200
| From | Bjorn Helgaas <bhelgaas@google.com> |
|---|---|
| Date | 2015-06-18 01:10 +0200 |
| Subject | Re: [PATCH 0/2] x86/PCI: enable pci=use_crs for more machines |
| Message-ID | <pCuD0-7ml-21@gated-at.bofh.it> |
On Tue, Jun 16, 2015 at 11:55 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> We have a few reports of sound devices not working because the BIOS didn't
> assign space for the device and the PCI core put it at an address that
> doesn't work.
>
> The Foxconn system has two PCI host bridges, and without the information
> from _CRS, the PCI core assigns space under the wrong bridge.
>
> We also have reports from pre-2008 systems (where we normally ignore _CRS)
> that support more than 32 physical address bits. After d56dbf5bab8c ("PCI:
> Allocate 64-bit BARs above 4G when possible"), we prefer to use that high
> space when we can, but it seems the host bridge doesn't respond to it.
>
> _CRS tells us how to avoid both problems, so these patches enable it for
> these cases.
>
> ---
>
> Bjorn Helgaas (2):
> x86/PCI: Use host bridge _CRS info on Foxconn K8M890-8237A
> x86/PCI: Use host bridge _CRS info on systems with >32 bit addressing
I applied both patches to pci/resource for v4.2.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web