> * v3.19 ignored [io 0x0cf8-0x0cff], but v4.0 includes it. I think > it's wrong to include it because that's the configuration space > address/data registers, so it's consumed by the host bridge and not > produced on the downstream side. > > * v3.19 includes [mem 0x7ff00000-0xfebfffff], but v4.0 does not. This > is what's screwing up the devices. > > I think all the windows should be marked as ACPI_PRODUCER in _CRS > since the space is "produced" on the downstream side of the bridge. > The [io 0x0cf8-0x0cff] region should probably be marked > ACPI_CONSUMER, and maybe that accounts for why v3.19 ignores it. But > I haven't found the code that does that yet. > > I suspect this is all related to the ACPI resource parsing rework. I > looked through that briefly, but no issues jumped out at me, so this > is just a heads-up in case it is obvious to you guys. > > Dave, it'd be useful if you could collect an acpidump so we can look > at the _CRS data in more detail. acpidump fails here with a /dev/mem warning in the kernel, now I'm not near the machine again until next week most likely, so I only have ssh for now, and the kernel it is running for which I don't have the source anymore! is there any of tables from /sys I can grab instead? Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
