From: Hollis Blanchard <hollisb@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5765] uImage: only try to load 'kernel' images (Hollis Blanchard)
Date: Thu, 20 Nov 2008 17:37:57 -0600 [thread overview]
Message-ID: <1227224277.16341.19.camel@localhost.localdomain> (raw)
In-Reply-To: <36864959917-BeMail@laptop>
On Thu, 2008-11-20 at 23:29 +0100, François Revol wrote:
> > IH_TYPE_STANDALONE images could be loaded, but would unexpectedly
> > fail if they
> > tried to use any uboot services.
>
> Hmm how is it planned to support the external API that is being
> developped ?
> It's being added for NetBSD IIRC, and I'll probably need that for Haiku
> as well, or use the boot loader as a standalone image.
I don't know anything about it, but assuming you mean a runtime API
u-boot offers to applications it's loaded, I don't see that qemu needs
to be involved at all.
> We would still have an u-boot rom around anyway, wouldn't we?
It's possible to implement the API in qemu itself (using a magic
"call-out" instruction), but running u-boot itself inside the VM is the
best option. (At one point Jocelyn claimed that this already works with
qemu's 405 emulation, but I could never get it to work.)
The code that I've posted is specifically to load uImages, so it
wouldn't be used to load u-boot itself. In the Bamboo patches I'm
working on, I just replicate the post-load environment u-boot leaves
behind (register state, device tree, kernel load address, TLB entries,
etc). This bypasses the need for a u-boot ROM.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-11-20 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 22:15 [Qemu-devel] [5765] uImage: only try to load 'kernel' images (Hollis Blanchard) Anthony Liguori
2008-11-20 22:29 ` François Revol
2008-11-20 23:37 ` Hollis Blanchard [this message]
2008-11-21 0:30 ` Jean-Christophe PLAGNIOL-VILLARD
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=1227224277.16341.19.camel@localhost.localdomain \
--to=hollisb@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.