Re: [Qemu-devel] [RfC PATCH 0/3] option rom loading via fw_cfg

[Alexander Graf <agraf@suse.de>]

Gerd Hoffmann wrote:
> 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

I was wondering if you were completely changing the semantics of the rom
infrastructure. Currently a rom is a synonym for "load this chunk of
memory on bootup".

With elf binaries, we're currently always creating "rom" chunks. What we
do in the multiboot code is to take those rom chunks and put them in a
fw_cfg variable.

I just wanted to make sure you're aware of that concept and don't
accidently break it :-).

>
> 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).

Ok :-). I would've reassured myself before writing this mail, but the
important patch implementing those parts is 2/3.

Alex