From: "Andreas Färber" <afaerber@suse.de>
To: Andrew Towers <atowers@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH v2] ARM: Permit any ARMv6K CPU to read the MVFR0 and MVFR1 VFP registers.
Date: Thu, 29 Mar 2012 15:10:17 +0200 [thread overview]
Message-ID: <4F745F39.2020006@suse.de> (raw)
In-Reply-To: <1333024868-1336-1-git-send-email-atowers@gmail.com>
Am 29.03.2012 14:41, schrieb Andrew Towers:
> This patch replaces the ARM_FEATURE_VFP3 test when reading MVFR registers
> with a test for a new feature flag ARM_FEATURE_MVFR, and sets this feature
> for all ARMv6K cores (ARM1156 is not a v6K core, yet supports MVFR; qemu
> does not support ARM1156 at this time.)
>
> MVFR0 and MVFR1 were introduced in ARM1136JF-S r1p0 (ARMv6K, VFPv2) and are
> present in ARM1156T2F-S (non-v6K), ARM1176JZF-S, ARM11MPCore and newer cores.
> Reference: ARM DDI 0211H, 0290G, 0301H, 0360E.
> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0211h/Ffbefjag.html
>
> Without this change, the linux kernel will not boot with VFP support enabled
> under ARM1176 system emulation, due to the unconditional use of MVFR1 at the
> end of vfp_init() in arch/arm/vfp/vfpmodule.c:
>
> VFP support v0.3: implemetor 41 architecture 1 part 20 variant b rev 5
> Internal error: Oops - undefined instruction: 0 [#1]
>
> Signed-off-by: Andrew Towers <atowers@gmail.com>
Feature inference looks good,
Reviewed-by: Andreas Färber <afaerber@suse.de>
> ---
>
> v2:
> * introduced ARM_FEATURE_MVFR, implied by ARM_FEATURE_V6K.
>
> Paul: I'd love to work on an rPi board model, and I'll see what I can put
> together, but much of the hardware is under NDA and I'm not in the loop..
You might find the partial bcm2835 manual helpful:
http://www.raspberrypi.org/archives/615
Open-source drivers (esp. Linux) are also often a helpful source for
emulating NDA'ed hardware.
Regards,
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-03-29 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 14:37 [Qemu-devel] [PATCH] ARM: Permit any ARMv6K CPU to read the MVFR0 and MVFR1 VFP registers Andrew Towers
2012-03-28 15:24 ` Peter Maydell
2012-03-29 12:41 ` [Qemu-devel] [PATCH v2] " Andrew Towers
2012-03-29 13:10 ` Andreas Färber [this message]
2012-03-29 13:46 ` 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=4F745F39.2020006@suse.de \
--to=afaerber@suse.de \
--cc=atowers@gmail.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).