From: Fabien Chouteau <chouteau@adacore.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Paul Brook" <paul@codesourcery.com>,
"Andreas Färber" <afaerber@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [ARM] Cortex-R4F and VFP3-D16
Date: Fri, 01 Mar 2013 13:07:22 +0100 [thread overview]
Message-ID: <513099FA.90605@adacore.com> (raw)
In-Reply-To: <CAFEAcA_T9g+fV=1m2o2KW1yEEEUysCLBUdeB2gy9Bz2Qzr5kYg@mail.gmail.com>
On 03/01/2013 12:32 PM, Peter Maydell wrote:
> On 1 March 2013 11:21, Fabien Chouteau <chouteau@adacore.com> wrote:
>> TMS570LS31x/21x Technical Reference Manual:
>>
>> "The TMS570 family is based on the ARM® CortexTM-R4F core. ARM has
>> designed this core to be used in big-endian and little-endian systems.
>> For the TI TMS570 family, the endianness has been configured to BE32."
>
> That is confusing, because ARM's R4F Technical Reference Manual
> says "The processor does not support word-invariant big-endianness
> (BE)-32"...
>
> (http://translatedcode.wordpress.com/2012/04/02/this-end-up/
> has a quick summary of what the various flavours of ARM
> endianness actually mean.)
>
Confusing indeed. It seems that the documentation is not reliable. Below
the text I just quoted, there's an example showing that TMS570 is
actually BE8. And this is confirmed by our experience using the real
board.
> I think you're going to have to run some tests on the actual
> hardware to find out what it really does. Specifically, what
> are the values of SCTLR.IE, SCTLR.EE and CPSR.E when you think
> you're in big-endian mode? (We need to sort out what parts of
> the behaviour you're seeing are the CPU itself and what parts
> are the SoC/board doing endianness flipping externally to the
> CPU.)
>
SCTLR.IE and SCTLR.EE are both set to 1 at reset and the values cannot
be changed.
BTW, our run-time works both on QEMU and a real-board, that's also why
I'm confident that there are no endianness issue.
Regards,
--
Fabien Chouteau
next prev parent reply other threads:[~2013-03-01 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <512E3637.6070609@adacore.com>
[not found] ` <CAFEAcA8gyz=b4xFW9NfqnLJx=azJwUovCDg_j3m5Gq-tyjze0Q@mail.gmail.com>
[not found] ` <512E4170.4070003@adacore.com>
[not found] ` <201302272049.59409.paul@codesourcery.com>
[not found] ` <512F6336.6090206@adacore.com>
[not found] ` <CAFEAcA8Ah2JQSA3XxWA=qbzecrcKXgNx-=gtaC9bfoFTuusq5g@mail.gmail.com>
[not found] ` <512F965B.1000007@adacore.com>
[not found] ` <CAFEAcA8fzFnDb-MDh5Wo3X77qwc-TnU-M4yvzBejNu2394LAmg@mail.gmail.com>
2013-03-01 10:13 ` [Qemu-devel] [ARM] Cortex-R4F and VFP3-D16 Fabien Chouteau
2013-03-01 10:40 ` Peter Maydell
2013-03-01 11:21 ` Fabien Chouteau
2013-03-01 11:32 ` Peter Maydell
2013-03-01 12:07 ` Fabien Chouteau [this message]
2013-03-01 12:16 ` Peter Maydell
2013-03-01 13:43 ` Fabien Chouteau
2013-03-01 15:10 ` Fabien Chouteau
2013-03-01 15:22 ` Peter Maydell
2013-03-01 18:54 ` Andreas Färber
2013-03-04 9:58 ` Fabien Chouteau
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=513099FA.90605@adacore.com \
--to=chouteau@adacore.com \
--cc=afaerber@suse.de \
--cc=paul@codesourcery.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).