On 4/29/09, Hollis Blanchard wrote:
> On Wed, 2009-04-29 at 12:38 -0500, Anthony Liguori wrote:
> > Hollis Blanchard wrote:
> > > On Wed, 2009-04-29 at 12:38 +0200, Jan Kiszka wrote:
> > >
> > >> What is the alignment of those regions then? None? And do regions of
> > >> different types overl
On 2/27/09, Liu Yu-B13201 wrote:
>
>
> > -Original Message-
> > From: Blue Swirl [mailto:blauwir...@gmail.com]
> > Sent: Friday, February 27, 2009 2:47 AM
> > To: Liu Yu-B13201
> > Cc: qemu-de...@nongnu.org; aurel...@aurel32.net;
> > h
On 2/26/09, Liu Yu wrote:
> MPIC and OpenPIC have very similar design.
> So a lot of code can be reused.
>
> Modification mainly include:
> 1. keep struct openpic_t to the maximum size of both MPIC and OpenPIC.
> 2. endianess swap.
>MPIC has the same endianess as target, so no need to swap
On 2/20/09, Aurelien Jarno wrote:
> On Tue, Feb 17, 2009 at 04:55:51PM +0200, Blue Swirl wrote:
> > On 2/17/09, Liu Yu wrote:
> > > MPIC and OpenPIC have very similar design.
> > > So a lot of code can be reused.
> > >
> > > Modification mainly
On 2/17/09, Liu Yu wrote:
> This patch add emulation of MPC8544DS board.
> And it can work on All E500 platforms.
>
> Signed-off-by: Liu Yu
> + * Copyright (C) 2009 Freescale Semiconductor, Inc. All rights reserved.
Again, "All rights reserved" is not what GPL says.
> +ret = kvmppc_rea
On 2/17/09, Liu Yu wrote:
> This patch add the emulation of freescale's pci controller for E500 platform.
>
> Signed-off-by: Liu Yu
A reset function (registered with qemu_register_reset) would be nice.
> + * Copyright (C) 2009 Freescale Semiconductor, Inc. All rights reserved.
"All rights re
On 2/17/09, Liu Yu wrote:
> MPIC and OpenPIC have very similar design.
> So a lot of code can be reused.
>
> Modification mainly include:
> 1. keep struct openpic_t to the maximum size of both MPIC and OpenPIC.
> 2. endianess swap.
>MPIC has the same endianess as target, so no need to swap
On 12/11/08, Hollis Blanchard wrote:
> Since most IO devices are integrated into the 440EP chip, "Bamboo support"
> mostly entails implementing the -kernel, -initrd, and -append options.
>
> These options are implemented by loading the guest as if u-boot had done it,
> i.e. loading a flat devic
