Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1534670 > unrolled thread
| Started by | Jon Masters <jcm@redhat.com> |
|---|---|
| First post | 2016-12-02 06:00 +0100 |
| Last post | 2016-12-02 06:00 +0100 |
| 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: [PATCHv2] PCI: QDF2432 32 bit config space accessors Jon Masters <jcm@redhat.com> - 2016-12-02 06:00 +0100
| From | Jon Masters <jcm@redhat.com> |
|---|---|
| Date | 2016-12-02 06:00 +0100 |
| Subject | Re: [PATCHv2] PCI: QDF2432 32 bit config space accessors |
| Message-ID | <sJO70-7cp-5@gated-at.bofh.it> |
On 11/03/2016 10:00 AM, Bjorn Helgaas wrote: > It turns out that we can't use the _CRS of host bridges because of the > Producer/Consumer bit screwup [1]. So the fallback is to include the > ECAM space in the _CRS of a PNP0C02 device. This is what the PCI > Firmware spec r3.0, Table 4-2, footnote 2 is talking about. > > Bjorn > > [1] The original ACPI spec intent was that Consumer resources would be > space like ECAM that is consumed directly by the bridge, and Producer > resources would be the windows forwarded down to PCI. But BIOSes > didn't use the Producer/Consumer bit consistently, so we have to > assume that all resources in host bridge _CRS are windows, which > leaves us no way to describe the Consumer resources. Aside - and now I realize you'd called this out as recently as last month. Alas the HPE m400 I reference on the other thread about the APM quirks doesn't have the motherboard resource entry so we're stuck with exactly the situation you describe above there. Jon. -- Computer Architect | Sent from my Fedora powered laptop
Back to top | Article view | linux.kernel
csiph-web