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: "Blue Swirl" <blauwirbel@gmail.com>,
	"Andreas Färber" <andreas.faerber@web.de>,
	Lluís <xscript@gmx.net>,
	"qemu-devel Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Multi heterogenous CPU archs for SoC sim?
Date: Sat, 22 Oct 2011 00:05:05 +0200	[thread overview]
Message-ID: <4EA1EC91.6050705@web.de> (raw)
In-Reply-To: <CAFEAcA85UyU1x-H_f7JFxs6Hw8hdDyWPAd77JP1DHX3fDqiFVg@mail.gmail.com>

Am 21.10.2011 08:58, schrieb Peter Maydell:
> On 20 October 2011 23:51, Andreas Färber <andreas.faerber@web.de> wrote:
>> Renesas announced
>> the R-Car H1 this week, a SoC with one SH4A core and four ARM Cortex-A9
>> cores.
> 
> Does it expose the SH4 to apps/OSes, or is it mostly used for
> power management or similar ignorable duties?

The predecessors were all SuperH based only, and the ARM cores don't
seem to have VFPv3 so the SH4A would feature a 128-bit FPU.
As for what automative customers may do with it once available, I have
no clue. My focus is on investigating where QEMU has architectural
shortcomings or undocumented assumptions blocking embedded development
and addressing these.

> (For several
> of the ARM boards we currently just ignore the fact that the real
> h/w has a Cortex-M3 doing power management type stuff.)

Mind to share which boards? I'm only aware of the NXP LPC43xx asymmetric
SoC (Cortex-M4 + Cortex-M0), which still is in development stage. The
datasheet doesn't really enlighten me how such a combo is supposed to
work in shared memory: Do all ARM cores share a reset vector (or what
you call it on arm) so that one has to branch based on CPUID to do
different tasks on different cores?

Andreas

  parent reply	other threads:[~2011-10-21 22:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 18:44 [Qemu-devel] Multi heterogenous CPU archs for SoC sim? Greg McGary
2011-05-25 19:20 ` Peter Maydell
2011-05-26 19:11   ` Blue Swirl
2011-05-26 20:07     ` Lluís
2011-05-26 20:31       ` Blue Swirl
2011-05-27 14:23         ` Lluís
2011-10-20 22:51     ` Andreas Färber
2011-10-21  6:58       ` Peter Maydell
2011-10-21  7:26         ` 陳韋任
2011-10-21 20:36           ` Andreas
2011-10-22  8:12             ` 陳韋任
2011-10-21 15:41         ` Lluís Vilanova
2011-10-21 22:05         ` Andreas Färber [this message]
2011-10-22  9:32           ` Peter Maydell
2011-05-26 20:10 ` Andreas Färber

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=4EA1EC91.6050705@web.de \
    --to=andreas.faerber@web.de \
    --cc=blauwirbel@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=xscript@gmx.net \
    /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).