qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Is realview-pb-a8 fully supported ?
Date: Sun, 9 Oct 2011 14:06:23 +0200	[thread overview]
Message-ID: <CAC9WiBhTbysHJm__hfCBiw99Sr_KA0YEmReuVe0B_zEG-1xQFg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA8V6=Vpb_gANWqpf4be2Abt2g1STDvYuaTVmeJBxoQ=Vw@mail.gmail.com>

Hello Peter,

On Sun, Oct 9, 2011 at 12:48 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 9 October 2011 09:28, Francis Moreau <francis.moro@gmail.com> wrote:
>> I'm trying to use qemu to emulate the ARM realview-pb-a8 and more
>> specifically I'd like to boot using the SD interface.
>>
>> However it looks like some devices are not emulated at all on this
>> platform.
>
> Correct; not all devices are emulated.
>

May I suggest to report that a platform is partially supported when
doing "qemu -M ?"

>> The "mmci" host driver needs some gpio in order to work.
>>
>> Is that correct that with qemu 0.14.1, I can't use the SD card interface ?
>
> You need a newer QEMU. The GPIO modules and the wiring for
> the MMC card status outputs should be present in QEMU 0.15.
> 0.14.1 has a number of known ARM bugs (especially in Neon
> and VFP emulation) and I do not recommend it for ARM targets.

Yes that what I saw when trying the tip of qemu git repo.

However, those are still missing:

amba_device_register failed to register dev:smc
amba_device_register failed to register dev:sctl
amba_device_register failed to register dev:wdog
amba_device_register failed to register dev:sci0
amba_device_register failed to register dev:ssp0
amba_device_register failed to register fpga:aaci

In your opinion, which plateform should I use to get a fully supported
platform based on ARMv7 cpu ?

> NB: when booting off SD card make sure you use
> "-drive if=sd,cache=writeback,file=your-sd.img", otherwise you
> will get the writethrough cache and really poor I/O performance.
> [the slight catch is that if your *host* system crashes you
> may get disk corruption, but typically for ARM emulation use
> cases that is acceptable.]

Thanks for the tip but why not making writeback the defaut ?
-- 
Francis

  reply	other threads:[~2011-10-09 12:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09  8:28 [Qemu-devel] Is realview-pb-a8 fully supported ? Francis Moreau
2011-10-09 10:48 ` Peter Maydell
2011-10-09 12:06   ` Francis Moreau [this message]
2011-10-09 12:51     ` Peter Maydell
2011-10-09 15:01       ` Alexander Graf
2011-10-09 15:46         ` Peter Maydell
2011-10-09 15:52           ` Alexander Graf
2011-10-09 16:22       ` Francis Moreau
2011-10-10  7:35         ` Francis Moreau
2011-10-10  8:42           ` Peter Maydell
2011-10-10 13:48             ` Francis Moreau
2011-10-12  9:23               ` Peter Maydell
2011-10-12 19:39                 ` Francis Moreau
2011-10-12 20:46                   ` Peter Maydell
2011-10-13  6:19                     ` Francis Moreau

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=CAC9WiBhTbysHJm__hfCBiw99Sr_KA0YEmReuVe0B_zEG-1xQFg@mail.gmail.com \
    --to=francis.moro@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).