From: "Andreas Färber" <afaerber@suse.de>
To: Doug Kwan <dougkwan@google.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: riku.voipio@iki.fi, agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH 3/3] configure: Add new target ppc64el-linux-user
Date: Thu, 08 May 2014 14:18:06 +0200 [thread overview]
Message-ID: <536B75FE.2090702@suse.de> (raw)
In-Reply-To: <1399537603-6905-4-git-send-email-dougkwan@google.com>
Am 08.05.2014 10:26, schrieb Doug Kwan:
> Add a new user mode target for little-endian PPC64.
>
> Signed-off-by: Doug Kwan <dougkwan@google.com>
> ---
> configure | 6 ++++++
> default-configs/ppc64el-linux-user.mak | 1 +
> 2 files changed, 7 insertions(+)
> create mode 100644 default-configs/ppc64el-linux-user.mak
>
> diff --git a/configure b/configure
> index ac2fa15..ce44044 100755
> --- a/configure
> +++ b/configure
> @@ -4917,6 +4917,12 @@ case "$target_name" in
> echo "TARGET_ABI32=y" >> $config_target_mak
> gdb_xml_files="power64-core.xml power-fpu.xml power-altivec.xml power-spe.xml"
> ;;
> + ppc64el)
In SUSE's build system and everywhere I read people talking about it,
including your 2/3, it's called ppc64le. Why did you choose ppc64el?
Regards,
Andreas
> + TARGET_ARCH=ppc64
> + TARGET_BASE_ARCH=ppc
> + TARGET_ABI_DIR=ppc
> + gdb_xml_files="power64-core.xml power-fpu.xml power-altivec.xml power-spe.xml"
> + ;;
> sh4|sh4eb)
> TARGET_ARCH=sh4
> bflt="yes"
> diff --git a/default-configs/ppc64el-linux-user.mak b/default-configs/ppc64el-linux-user.mak
> new file mode 100644
> index 0000000..6948225
> --- /dev/null
> +++ b/default-configs/ppc64el-linux-user.mak
> @@ -0,0 +1 @@
> +# Default configuration for ppc64el-linux-user
>
--
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:[~2014-05-08 12:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 8:26 [Qemu-devel] [PATCH 0/3] Adding new user mode target ppc64el-linux-user Doug Kwan
2014-05-08 8:26 ` [Qemu-devel] [PATCH 1/3] linux-user: Handle ELFv2 PPC64 binaries in user mode Doug Kwan
2014-05-08 8:36 ` Alexander Graf
2014-05-08 8:43 ` Doug Kwan (關振德)
2014-05-08 8:45 ` Alexander Graf
2014-05-08 13:30 ` Ulrich Weigand
2014-05-08 8:26 ` [Qemu-devel] [PATCH 2/3] PPC: Allow little-endian " Doug Kwan
2014-05-08 8:39 ` Alexander Graf
2014-05-08 8:49 ` Doug Kwan (關振德)
2014-05-08 8:55 ` Alexander Graf
2014-05-08 9:05 ` Doug Kwan (關振德)
2014-05-08 9:11 ` Alexander Graf
2014-05-08 9:24 ` Doug Kwan (關振德)
2014-05-08 12:39 ` Peter Maydell
2014-05-08 12:44 ` Alexander Graf
2014-05-08 8:26 ` [Qemu-devel] [PATCH 3/3] configure: Add new target ppc64el-linux-user Doug Kwan
2014-05-08 8:41 ` Alexander Graf
2014-05-08 8:46 ` Doug Kwan (關振德)
2014-05-08 8:56 ` Alexander Graf
2014-05-08 9:09 ` Doug Kwan (關振德)
2014-05-08 12:18 ` Andreas Färber [this message]
2014-05-08 12:28 ` Peter Maydell
2014-05-08 12:45 ` Alexander Graf
2014-05-08 15:57 ` Doug Kwan (關振德)
2014-05-08 14:41 ` Tom Musta
2014-05-08 15:19 ` Doug Kwan (關振德)
2014-05-08 15:25 ` Peter Maydell
2014-05-08 15:32 ` Doug Kwan (關振德)
2014-05-08 15:41 ` Peter Maydell
2014-05-08 15:51 ` Doug Kwan (關振德)
2014-05-08 15:56 ` Peter Maydell
2014-05-08 15:39 ` Tom Musta
2014-05-08 15:43 ` Peter Maydell
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=536B75FE.2090702@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=dougkwan@google.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).