From: Gerd Hoffmann <kraxel@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RfC PATCH 0/3] option rom loading via fw_cfg
Date: Thu, 17 Dec 2009 10:34:28 +0100 [thread overview]
Message-ID: <4B29FB24.9010106@redhat.com> (raw)
In-Reply-To: <37726A1E-223A-4C5D-ABC0-301A1D0E493C@suse.de>
On 12/17/09 00:47, Alexander Graf wrote:
>
> Am 16.12.2009 um 18:46 schrieb Gerd Hoffmann <kraxel@redhat.com>:
>
>> Hi,
>>
>> quick draft of a file xfer api for fw_cfg, qemu side only, not tested
>> yet, to be used for option roms.
>>
>> comments?
>
> 2/3 is missing here.
Hmm, I got it via qemu-devel. Maybe it is just delayed for you.
> How does elf rom loading come into play here? We'll need both - a
> firmware rom blob (openbios) and a fw_cfg rom blob for elf (multiboot).
--verbose please
Do you talk about ppc?
Current rom loading code will stay, we can't drop it. We might be able
to simplify it a bit some day when all option rom loading goes via
seabios because everything but option roms will be loaded at a fixed
address. But seabios itself can't be loaded via fw_cfg (chicken, egg).
cheers,
Gerd
next prev parent reply other threads:[~2009-12-17 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 17:46 [Qemu-devel] [RfC PATCH 0/3] option rom loading via fw_cfg Gerd Hoffmann
2009-12-16 17:46 ` [Qemu-devel] [PATCH 1/3] fw_cfg: make calls typesafe Gerd Hoffmann
2009-12-16 17:46 ` [Qemu-devel] [PATCH 2/3] fw_cfg: file xfer api Gerd Hoffmann
2009-12-16 17:46 ` [Qemu-devel] [PATCH 3/3] roms: use fw_cfg " Gerd Hoffmann
2009-12-16 23:47 ` [Qemu-devel] [RfC PATCH 0/3] option rom loading via fw_cfg Alexander Graf
2009-12-17 9:34 ` Gerd Hoffmann [this message]
2009-12-17 10:27 ` Alexander Graf
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=4B29FB24.9010106@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--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).