Hi Arnd, On Mon, Apr 14, 2014 at 07:48:17PM +0100, Arnd Bergmann wrote: > On Monday 14 April 2014 18:13:00 Will Deacon wrote: > > Arnd: Is there anything more you'd like me to do with this series? Given > > that it would be targetting 3.16, there's still plenty of time to make > > changes (we talked about extracting some library functions in the past). > > I don't remember the latest status of your patch set, but you might want > to read the discussions we had about Liviu's patches last week. The latest status (v5) was that I had something working (I got hung up on the I/O offset handing), with all feedback addressed. The next step was to try and move parts into library code, but it looks like Liviu is handling a lot of that with his arm64 stuff. > We still haven't figured out exactly how to handle I/O space in the common > code, but I think we are making progress. The discussions certainly seem to be making progress. > We also have discussed some ideas about how to restructure the PCI > code layer to make it easier to share host drivers across architectures > and clean up the interfaces in the process. Ok. Whilst this all sounds good from an arm64 perspective (with Liviu currently doing the work), it's not clear to me where that leaves my 32-bit ARM kvmtool code. That was the main reason for me writing this driver, and it seems a shame to have to wait for all the generic code to be sorted out before it can be used on AArch32, where there is already a functional pcibios implementation. The discussions mention things like generic pci_host_bridge_ops, but having that for arch/arm/ doesn't sound like something that is imminent. Of course, I plan to port my driver to the new infrastructure when it lands (since I want to support arm64), but it would be good to have something for AArch32 in the meantime. Will -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
