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 11:13:26 +0100 [thread overview]
Message-ID: <51307F46.4080606@adacore.com> (raw)
In-Reply-To: <CAFEAcA8fzFnDb-MDh5Wo3X77qwc-TnU-M4yvzBejNu2394LAmg@mail.gmail.com>
On 02/28/2013 07:42 PM, Peter Maydell wrote:
> On 28 February 2013 17:39, Fabien Chouteau <chouteau@adacore.com> wrote:
>> On 02/28/2013 03:16 PM, Peter Maydell wrote:
>>> On 28 February 2013 14:01, Fabien Chouteau <chouteau@adacore.com> wrote:
>>>> In fact I'm
>>>> working on a big-endian R4F (TMS570) and I have endianness issue in the
>>>> communication with GDB.
>>>
>>> If you're also trying to get big-endian mode to work (linux-user
>>> mode or system emulation?) you may have more problems than merely
>>> implementing R4 support or VFP-D16 :-)
>
>> I already built qemu-system-armeb, and implemented few devices of the
>> TMS570 (rti, sci, and vim). Besides this GDB issue I have no endianness
>> problem so far.
>
> This is probably some combination of luck and insufficient testing.
> If you submit some patches I will review them :-)
>
Well my goal is not to test every ARM cpu and every devices in big-endian.
I only need a small subset of TMS570: - Cortex-R4F without MPU
- Timers (RTI)
- Serial port (SCI)
- Interrupt manager (RTI)
and everything works good so far.
> How are you handling the SCTLR IE and EE bits?
>
I did nothing, as far as I know it's not possible to switch endianness
in QEMU. TMS570 are configured for big-endian only, so this is not a
problem for me.
>>> Are you planning to do the v7 PMSA support?
>
>> I don't know what that is, but I'll take a look :)
>
> It's the Memory Protection Unit -- QEMU currently only has the
> old v5 MPU, and register_cpu_regs_for_features() will assert
> if your CPU is v6 or v7 and has the FEATURE_MPU bit set.
> If you're putting in system emulation for an R4 then you must
> implement this (and I'm surprised you've managed to get anything
> significant to run without it).
>
The programs I run don't need MPU, so for the moment I have no plan to
implement PMSA.
Regards,
--
Fabien Chouteau
next parent reply other threads:[~2013-03-01 10:13 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 ` Fabien Chouteau [this message]
2013-03-01 10:40 ` [Qemu-devel] [ARM] Cortex-R4F and VFP3-D16 Peter Maydell
2013-03-01 11:21 ` Fabien Chouteau
2013-03-01 11:32 ` Peter Maydell
2013-03-01 12:07 ` Fabien Chouteau
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=51307F46.4080606@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).