From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Zheng.Wang@infineon.com
Subject: Re: [Qemu-devel] Inquring about Arm11mpcore
Date: Wed, 15 Jul 2009 11:49:09 +0100 [thread overview]
Message-ID: <200907151149.10228.paul@codesourcery.com> (raw)
In-Reply-To: <4A5C556FA5C54142AE33C414481CE79C16E2B88F1D@mucse404.eu.infineon.com>
On Wednesday 15 July 2009, Zheng.Wang@infineon.com wrote:
> Hello all,
>
> I have used qemu-0.10.5 to emulate kernel 2.6.24 on arm11mpcore of realview
> platform
Make sure you're using the right board. qemu emulates a revB Emulation
Baseboard plus core tile. This should work out the box. Other boards almost
certainly won't work. One symptom may be that the interrupt routing will be
wrong, which is consistent with your symptoms.
Paul
next prev parent reply other threads:[~2009-07-15 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 10:37 [Qemu-devel] Inquring about Arm11mpcore Zheng.Wang
2009-07-15 10:49 ` Paul Brook [this message]
2009-08-13 11:16 ` [Qemu-devel] " Antti P Miettinen
2009-08-17 14:23 ` Antti P Miettinen
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=200907151149.10228.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=Zheng.Wang@infineon.com \
--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).