From: Karthik <karthikshanmugam@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ARM Cortex R5 + VFP3
Date: Wed, 25 May 2016 11:00:36 +0530 [thread overview]
Message-ID: <CAAmr2Y8twayZRBGYB19e1z0-zX-Yve5D5fHzD7OevFv+opCrSw@mail.gmail.com> (raw)
In-Reply-To: <CAAmr2Y8nHTtb+H1sZwdjTyJOMAG2GHpdYwq5-MxMidqsufY8=Q@mail.gmail.com>
Hi,
Added enabling VFP co-processor in the bootrom emulation code. Works like a
charm.
Many thanks.
Best regards,
Karthik
On Tue, May 24, 2016 at 7:52 PM, Karthik <karthikshanmugam@gmail.com> wrote:
> Yeah, the micro had a secure boot ROM which we don't have access to.
> Probably it is enabled there. I'll check in the target hardware.
>
> The code generated by the compiler doesn't specifically check for
> non-existent registers, so we should be good using VFP3 in place for
> VFP3-D16.
>
> Best regards,
> Karthik
> On May 24, 2016 7:31 PM, "Peter Maydell" <peter.maydell@linaro.org> wrote:
>
>> On 24 May 2016 at 14:49, Karthik <karthikshanmugam@gmail.com> wrote:
>> > ahh okay. The code I don't think writes to CPACR_EL1 register, but it
>> runs
>> > on the hardware anywary.
>>
>> If it does then there's probably some firmware somewhere
>> which is doing the setup for you somehow.
>>
>> As you can see in the Cortex-R5 technical reference manual entry
>> for CPACR:
>>
>> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0205g/Bgbjhiea.html
>>
>> the hardware reset value for bits 21..23 is 0, meaning access denied,
>> and for FPEXC the EN bit is clear on reset:
>>
>> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0205g/Bgbjhiea.html
>>
>> By the way, QEMU doesn't implement VFPv3-D16, which is what the R5
>> ought to have -- setting the ARM_FEATURE_VFP3 bit will give you
>> 32 double-precision registers. This is probably close enough that
>> guest code will work, though obviously if the guest specifically
>> tests that registers 16..31 don't exist it will not behave as
>> the hardware does.
>>
>> thanks
>> -- PMM
>>
>
prev parent reply other threads:[~2016-05-25 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 13:07 [Qemu-devel] ARM Cortex R5 + VFP3 Karthik
2016-05-24 13:37 ` Peter Maydell
2016-05-24 13:49 ` Karthik
2016-05-24 14:00 ` Peter Maydell
2016-05-24 14:22 ` Karthik
2016-05-25 5:30 ` Karthik [this message]
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=CAAmr2Y8twayZRBGYB19e1z0-zX-Yve5D5fHzD7OevFv+opCrSw@mail.gmail.com \
--to=karthikshanmugam@gmail.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).