From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org,
Mark Langsdorf <mark.langsdorf@calxeda.com>
Subject: Re: [Qemu-devel] [PATCH RFC for-1.2] arm: Move some ARM devices into libhw
Date: Thu, 02 Aug 2012 17:58:05 +0200 [thread overview]
Message-ID: <501AA38D.4020709@suse.de> (raw)
In-Reply-To: <CAFEAcA-gHk0m3Gm-ifBXkg82gsYGduwhuhC4X2ScfOXD_-g5-A@mail.gmail.com>
Am 02.08.2012 17:01, schrieb Peter Maydell:
> On 2 August 2012 15:53, Andreas Färber <afaerber@suse.de> wrote:
>> In practice, it seemed that usage of these devices is rather fragmented
>> (not all boards use all PLxxx devices) so that per-device config names
>> as in master allow for fine-grained control of which devices get built
>> if only armeb-softmmu were to be built;
>> on the other hand if that seems too complicated the alternative question
>> to ask would be, are all PLxxx devices theoretically capable of being
>> used for armeb as well?
>
> They should in theory be OK on a big-endian system, but then in theory
> just about any device should be OK on a big endian system: device/system
> endianness and CPU endianness are orthogonal.
I was specifically thinking of whether the specified device endianness
is correct, i.e. whether device code assumes Little Endian but might be
marked DEVICE_NATIVE_ENDIAN (thus becoming Big Endian on armeb) or is
marked DEVICE_LITTLE_ENDIAN but should be DEVICE_NATIVE_ENDIAN to adapt
to armeb (e.g., double-swapping issues with IBM8514 card a while ago).
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-08-02 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 1:16 [Qemu-devel] [PATCH RFC for-1.2] arm: Move some ARM devices into libhw Andreas Färber
2012-08-02 13:48 ` Peter Maydell
2012-08-02 14:53 ` Andreas Färber
2012-08-02 15:01 ` Peter Maydell
2012-08-02 15:58 ` Andreas Färber [this message]
2012-08-10 17:15 ` Andreas Färber
2012-08-11 19:12 ` 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=501AA38D.4020709@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=mark.langsdorf@calxeda.com \
--cc=pbonzini@redhat.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).