qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <andreas.faerber@web.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: giancarlo.asnaghi@st.com, qemu-devel@nongnu.org,
	Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [RFC v2 1/2] target-arm: Prepare support for Cortex-R4
Date: Sat, 22 Sep 2012 15:56:24 +0200	[thread overview]
Message-ID: <505DC388.9060505@web.de> (raw)
In-Reply-To: <CAFEAcA97DWN0aqBo8YPLwsXJUxY=Z4tVEhsK79CojSL4EP7Emg@mail.gmail.com>

Am 22.09.2012 15:05, schrieb Peter Maydell:
> On 22 September 2012 12:45, Andreas Färber <andreas.faerber@web.de> wrote:
>> +static void cortex_r4_initfn(Object *obj)
>> +{
>> +    ARMCPU *cpu = ARM_CPU(obj);
>> +    set_feature(&cpu->env, ARM_FEATURE_V7);
>> +    set_feature(&cpu->env, ARM_FEATURE_THUMB_DIV);
>> +    set_feature(&cpu->env, ARM_FEATURE_MPU);
> 
> This will trip the assert in register_cp_regs_for_features():

Thanks for the pointer. This rebased version is only compile-tested and
is provided mainly for the ST guys to build upon, during my absence.

>     if (arm_feature(env, ARM_FEATURE_MPU)) {
>         /* These are the MPU registers prior to PMSAv6. Any new
>          * PMSA core later than the ARM946 will require that we
>          * implement the PMSAv6 or PMSAv7 registers, which are
>          * completely different.
>          */
>         assert(!arm_feature(env, ARM_FEATURE_V6));
> 
> ...indicating that R4 support is more work than is contained
> in this patch :-)

...which confirms what I stated in the message this is threaded to, and
is reflected by "prepare". :)

Same for VFPv3-D16 in the second RFC patch (which used to "add" to
cortex-r4, now should've been updated to "prepare" as well).

And of course the Cortex-R4's lock-step mode that seems to make it so
interesting for automotive customers.

/-F

  reply	other threads:[~2012-09-22 13:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 15:15 [Qemu-devel] ARM Cortex-R4 support ? Giancarlo ASNAGHI
2012-09-21 17:05 ` Andreas Färber
2012-09-22 11:45   ` [Qemu-devel] [RFC v2 1/2] target-arm: Prepare support for Cortex-R4 Andreas Färber
2012-09-22 11:45     ` [Qemu-devel] [RFC v2 2/2] target-arm: Add support for Cortex-R4F Andreas Färber
2012-09-22 14:43       ` Blue Swirl
2012-09-22 14:54       ` Peter Maydell
2012-09-22 13:05     ` [Qemu-devel] [RFC v2 1/2] target-arm: Prepare support for Cortex-R4 Peter Maydell
2012-09-22 13:56       ` Andreas Färber [this message]
2012-09-22 14:30         ` Peter Maydell
2012-09-24  7:48   ` [Qemu-devel] ARM Cortex-R4 support ? Giancarlo ASNAGHI
2012-09-25  9:20   ` Giancarlo ASNAGHI

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=505DC388.9060505@web.de \
    --to=andreas.faerber@web.de \
    --cc=giancarlo.asnaghi@st.com \
    --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).