qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>,
	"Serge E. Hallyn" <serge@hallyn.com>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/1] Support ppc64le binfmt registration
Date: Wed, 27 Aug 2014 23:30:59 +0200	[thread overview]
Message-ID: <53FE4E13.1060803@suse.de> (raw)
In-Reply-To: <CAFEAcA_E0_vbX_kbNL=vzVeG01ZbEh2tAjSeBMOzcoD0Oo1kiQ@mail.gmail.com>



On 27.08.14 21:01, Peter Maydell wrote:
> [adding qemu-ppc]
> 
> On 27 August 2014 19:45, Serge E. Hallyn <serge@hallyn.com> wrote:
>> Quoting Peter Maydell (peter.maydell@linaro.org):
>>> On 27 August 2014 18:55, Serge E. Hallyn <serge@hallyn.com> wrote:
>>>> This is a part of a patch proposed by jaejunh at
>>>> https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1358268
>>>> which enables running ppc64le binaries through qemu-user.
>>>
>>> I'm confused -- wouldn't these be handled by the existing
>>> "ppc64le" support?
> 
>> It looks to me like the point was to add a TARGET_ABI32=y
>> version (and I dunno, something about CONFIG_LIBDECNUMBER=y
>> for 32-bit).
> 
> Wouldn't that be a "ppc64leabi32" target?

There is no LE support for 32bit on PPC :).


Alex

  reply	other threads:[~2014-08-27 21:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 17:55 [Qemu-devel] [PATCH 1/1] Support ppc64le binfmt registration Serge E. Hallyn
2014-08-27 18:20 ` Peter Maydell
2014-08-27 18:45   ` Serge E. Hallyn
2014-08-27 19:01     ` Peter Maydell
2014-08-27 21:30       ` Alexander Graf [this message]
2014-08-27 21:35         ` [Qemu-devel] [Qemu-ppc] " Peter Maydell
2014-08-27 22:40           ` Alexander Graf
2014-08-27 23:05             ` Serge E. Hallyn
2014-08-27 23:09               ` Serge E. Hallyn
2014-08-28  7:42                 ` 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=53FE4E13.1060803@suse.de \
    --to=agraf@suse.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=serge@hallyn.com \
    /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).