On 2/16/2016 8:53 AM, Tomasz Nowicki wrote: > From the functionality point of view this series might be split into the > following logic parts: > 1. Make MMCONFIG code arch-agnostic which allows all architectures to collect > PCI config regions and used when necessary. > 2. Move non-arch specific bits to the core code. > 3. Use MMCONFIG code and implement generic ACPI based PCI host controller driver. > 4. Enable above driver on ARM64 > > Patches has been built on top of 4.5-rc3 and can be found here: > git@xxxxxxxxxx:semihalf-nowicki-tomasz/linux.git (pci-acpi-v5) > > NOTE, this patch set depends on Lorenzo's fixes: > https://patchwork.ozlabs.org/patch/576450/ > which can be found in pci-acpi-v5 branch. > > This has been tested on Cavium ThunderX server, JunoR2, HP RX2660 IA64, x86, > Hip05, X-Gene and QEMU-aarch64. Any help in reviewing and testing is very appreciated. > > v4 -> v5 > - dropped MCFG refactoring group patches 1-6 from series v4 and integrated Jayachandran's patch > https://patchwork.ozlabs.org/patch/575525/ > - rewrite PCI legacy IRQs allocation > - squashed two patches 11 and 12 from series v4, fixed bisection issue > - changelog improvements > - rebased to 4.5-rc3 > > v3 -> v4 > - dropped Jiang's fix http://lkml.iu.edu/hypermail/linux/kernel/1601.1/04318.html > - added Lorenzo's fix patch 19/24 > - ACPI PCI bus domain number assigning cleanup > - changed resource management, we now claim and reassign resources > - improvements for applying quirks > - dropped Matthew's http://www.spinics.net/lists/linux-pci/msg45950.html dependency > - rebased to 4.5-rc1 > Having tested v4 and v5, I'm seeing some resource assignment problems and address conflicts. And problems booting QEMU. Anybody else seeing the same? -- Sinan Kaya Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- 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
