From: "Piotr Król" <pietrushnic@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vexpress-a9: coreboot is unable to push any data on stack
Date: Sat, 16 Aug 2014 11:50:18 +0200 [thread overview]
Message-ID: <20140816095017.GB25591@echad> (raw)
In-Reply-To: <CAFEAcA_d6G+s1fgRuO7YvX=xhOZ7fPnoptd0xsHO3-8g-p12wQ@mail.gmail.com>
On Fri, Aug 15, 2014 at 11:54:55PM +0100, Peter Maydell wrote:
> I'm not looking for advocacy, just for an explanation of what it's
> doing, and in particular whether anybody's ever tested this on real
> hardware. (Running guest code only on QEMU is a recipe for bugs,
> because our emulation is often not very accurate and if you only test
> on QEMU you can end up accidentally relying on our bugs.)
>
Creboot is an open source replacement for BIOS. Almost every supported
board contain its own memory map. According to commit message from
Chromium developer coreboot build for qemu vexpress-a9 was created to
'simplify testing ARM implementation (... and) to verify the boot loader
functionality'. I think that code for real hardware got little in common
with qemu implementation.
I'm trying to use this implementation for pure educational purposes.
Going back to my initial issues with stack, changing stack location to
SRAM improves situation but does not fix booting. It looks like whole
implementation assumes running from RAM.
> The common motherboard docs:
> http://infocenter.arm.com/help/topic/com.arm.doc.dui0447j/index.html
> A9 daughterboard docs:
> http://infocenter.arm.com/help/topic/com.arm.doc.dui0448h/index.html
> A15 daughterboard docs:
> http://infocenter.arm.com/help/topic/com.arm.doc.dui0604e/index.html
>
Thanks,
Piotr
next prev parent reply other threads:[~2014-08-16 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 10:07 [Qemu-devel] vexpress-a9: coreboot is unable to push any data on stack Piotr Król
2014-08-15 16:10 ` Peter Maydell
2014-08-15 18:02 ` Piotr Król
2014-08-15 22:54 ` Peter Maydell
2014-08-16 9:50 ` Piotr Król [this message]
2014-08-16 11:19 ` 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=20140816095017.GB25591@echad \
--to=pietrushnic@gmail.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).