[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] [PATCH 00/15] Sam460ex emulation

From: BALATON Zoltan
Subject: Re: [Qemu-ppc] [PATCH 00/15] Sam460ex emulation
Date: Sun, 27 Aug 2017 14:34:14 +0200 (CEST)
User-agent: Alpine 2.21 (BSF 202 2017-01-01)


Just to confirm where we are with this series, let me summarise what I got from the replies and what's my plan for this based on that. Here's the list of patches for reference:

[PATCH 01/15] ppc4xx: Move MAL from ppc405_uc to ppc4xx_devs
[PATCH 02/15] ppc4xx: Make MAL emulation more generic
[PATCH 03/15] ohci: Allow sysbus version to be used as a companion
[PATCH 04/15] ehci: Add ppc4xx-ehci for the USB 2.0 controller in embedded PPC 
[PATCH 05/15] ppc4xx: Split off 4xx I2C emulation from ppc405_uc to its own file
[PATCH 06/15] ppc4xx_i2c: QOMify
[PATCH 07/15] ppc4xx_i2c: Move to hw/i2c
[PATCH 08/15] ppc4xx_i2c: Implement basic I2C functions
[PATCH 09/15] hw/ide: Emulate SiI3112 SATA controller
[PATCH 10/15] ppc440: Add emulation of plb-pcix controller found in some 440 
[PATCH 11/15] ppc: Add 460EX embedded CPU
[PATCH 12/15] ppc4xx: Export ECB and PLB emulation
[PATCH 13/15] ppc4xx: Add more PLB registers
[PATCH 14/15] ppc4xx: Add device models found in PPC440 core SoCs
[PATCH 15/15] ppc: Add aCube Sam460ex board

- I think 1-7 is either already queued for 2.11 or could be applied as is having got reviews without need to change so I don't need to resend them. So are 11-13 if I got that right. That leaves 8-10 and 14-15 that I'll resend.

- I'm not sure if 8 was reviewed or do I need to make any modifications to it.

- I know I should change 9-10 and 14-15 based on review comments and resend.

Since I'll likely also need to change those patches to fix the bugs we know about currently, I thought I should probably resend after those bugs are fixed to avoid subsequent fixup patches. Since this will not be before next week (because I don't have time for it before that) I hope development should be open again and those patches that are already OK could be merged by then so I can rebase on that and only resend the missing ones as described above. Is that OK or did I miss something?

David, in case you want to stage all of this in your for-2.11 branch before all patches are ready and send them together, then where is this branch I should rebase to?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]