From: Li Guang <lig.fnst@cn.fujitsu.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/4] add sunxi machine
Date: Thu, 21 Nov 2013 07:55:07 +0800 [thread overview]
Message-ID: <528D4BDB.3040502@cn.fujitsu.com> (raw)
In-Reply-To: <CAFEAcA9XZ6d67M2Z3RKeWg04xZfCfQVxnNeG2FnKya4bbcS=kg@mail.gmail.com>
Hi, Peter
Peter Maydell wrote:
> On 20 November 2013 07:53, liguang<lig.fnst@cn.fujitsu.com> wrote:
>
>> this patch-set implemented a device-reduced
>> machine type for Allwinner's sunxi series SoC,
>> like sunxi-4i/5i/7i ...
>>
>
>> Li Guang (4)
>> hw/arm: add new machine type sunxi
>> hw/arm/sunxi-soc: add interrupt controller
>> hw/arm/sunxi-soc: add sunxi timer
>> hw/arm/sunxi-soc: really initialize sunxi machine
>>
> Hi. Thanks for this patch set. I see you've put all the code
> into one file in hw/arm, but we prefer each device model
> to go in its own file in the right subdirectory of hw/. So
> you put the interrupt controller under hw/intc/, the
> timer under hw/timer/, and only the top level board model
> lives under hw/arm. If you could restructure the
> patches this way that would be great.
>
> You'll also need to add VMState descriptions to your
> devices so they can be migrated.
>
>
OK, let me split it into 3 files, and try to add VMstate.
Thanks!
prev parent reply other threads:[~2013-11-20 23:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 7:53 [Qemu-devel] [PATCH 0/4] add sunxi machine liguang
2013-11-20 7:53 ` [Qemu-devel] [PATCH 1/4] hw/arm: add new machine type sunxi liguang
2013-11-20 7:53 ` [Qemu-devel] [PATCH 2/4] hw/arm/sunxi-soc: add interrupt controller liguang
2013-11-20 7:53 ` [Qemu-devel] [PATCH 3/4] hw/arm/sunxi-soc: add sunxi timer liguang
2013-11-20 7:53 ` [Qemu-devel] [PATCH 4/4] hw/arm/sunxi-soc: really initialize sunxi machine liguang
2013-11-20 9:26 ` [Qemu-devel] [PATCH 0/4] add " Peter Maydell
2013-11-20 23:55 ` Li Guang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=528D4BDB.3040502@cn.fujitsu.com \
--to=lig.fnst@cn.fujitsu.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).