From: "Andreas Färber" <afaerber@suse.de>
To: Guan Xuetao <gxt@mprc.pku.edu.cn>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 8/9] unicore32-softmmu: add config and makefile support
Date: Fri, 25 May 2012 13:48:26 +0200 [thread overview]
Message-ID: <4FBF718A.1040505@suse.de> (raw)
In-Reply-To: <307d86106f46f5781854708cc52cc2f83e63f119.1337944756.git.gxt@mprc.pku.edu.cn>
Am 25.05.2012 13:29, schrieb Guan Xuetao:
> This patch adds configure and makefile support for unicore32-softmmu.
> All puv3-soc devices are put into hw/pkunity directory, so this dir
> will be added when unicore32-softmmu is selected.
>
> Signed-off-by: Guan Xuetao <gxt@mprc.pku.edu.cn>
> ---
> Makefile.target | 5 +++++
> arch_init.c | 2 ++
> arch_init.h | 1 +
> configure | 4 ++++
> default-configs/unicore32-softmmu.mak | 4 ++++
> 5 files changed, 16 insertions(+), 0 deletions(-)
> create mode 100644 default-configs/unicore32-softmmu.mak
>
> diff --git a/Makefile.target b/Makefile.target
> index 1582904..2f850d3 100644
> --- a/Makefile.target
> +++ b/Makefile.target
> @@ -387,6 +387,11 @@ obj-xtensa-y += core-dc232b.o
> obj-xtensa-y += core-dc233c.o
> obj-xtensa-y += core-fsf.o
>
> +obj-unicore32-y += uc32_softmmu.o
> +obj-unicore32-y += pkunity/puv3.o
> +obj-unicore32-y += pkunity/puv3_intc.o pkunity/puv3_ost.o pkunity/puv3_gpio.o
> +obj-unicore32-y += pkunity/puv3_pm.o pkunity/puv3_dma.o
[snip]
You need to put the Makefile/configure changes into the patches that
introduce the files please, otherwise they cannot be checked for
compiler warnings/errors.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-05-25 11:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 11:28 [Qemu-devel] [PATCH 0/9] *** SUBJECT HERE *** Guan Xuetao
2012-05-25 11:28 ` [Qemu-devel] [PATCH 1/9] unicore32-softmmu: make exceptions generated in unicore32 architecture Guan Xuetao
2012-05-25 11:29 ` [Qemu-devel] [PATCH 2/9] unicore32-softmmu: implement some softmmu specific functions Guan Xuetao
2012-05-25 11:29 ` [Qemu-devel] [PATCH 3/9] unicore32-softmmu: add coprocessor 0 and ocd instruction support Guan Xuetao
2012-05-25 11:29 ` [Qemu-devel] [PATCH 4/9] unicore32-softmmu: make sure that kernel can access user space Guan Xuetao
2012-05-25 11:29 ` [Qemu-devel] [PATCH 5/9] unicore32-softmmu: initialize ucv2 cpu Guan Xuetao
2012-05-25 11:42 ` Andreas Färber
2012-05-28 9:43 ` guanxuetao
2012-05-28 13:14 ` Andreas Färber
2012-05-25 11:29 ` [Qemu-devel] [PATCH 6/9] unicore32-softmmu: add generic cpu state save/load functions Guan Xuetao
2012-05-25 11:44 ` Andreas Färber
2012-05-28 9:45 ` guanxuetao
2012-05-25 11:45 ` 陳韋任
2012-05-25 11:29 ` [Qemu-devel] [PATCH 7/9] unicore32-softmmu: add puv3 soc support Guan Xuetao
2012-05-25 11:46 ` Andreas Färber
2012-05-28 9:58 ` guanxuetao
2012-05-25 11:29 ` [Qemu-devel] [PATCH 8/9] unicore32-softmmu: add config and makefile support Guan Xuetao
2012-05-25 11:48 ` Andreas Färber [this message]
2012-05-28 10:08 ` guanxuetao
2012-05-28 13:46 ` Andreas Färber
2012-05-25 11:29 ` [Qemu-devel] [PATCH 9/9] unicore32-softmmu: add maintainer information Guan Xuetao
2012-05-25 11:30 ` [Qemu-devel] [PATCH 0/9] *** SUBJECT HERE *** Guan Xuetao
2012-05-25 12:09 ` Andreas Färber
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=4FBF718A.1040505@suse.de \
--to=afaerber@suse.de \
--cc=blauwirbel@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--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).