From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NLCkw-0004nC-A1
	for qemu-devel@nongnu.org; Thu, 17 Dec 2009 04:34:46 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NLCkr-0004jh-50
	for qemu-devel@nongnu.org; Thu, 17 Dec 2009 04:34:45 -0500
Received: from [199.232.76.173] (port=44461 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NLCkq-0004jR-V2
	for qemu-devel@nongnu.org; Thu, 17 Dec 2009 04:34:41 -0500
Received: from mx1.redhat.com ([209.132.183.28]:32119)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <kraxel@redhat.com>) id 1NLCkq-0003Rv-F9
	for qemu-devel@nongnu.org; Thu, 17 Dec 2009 04:34:40 -0500
Message-ID: <4B29FB24.9010106@redhat.com>
Date: Thu, 17 Dec 2009 10:34:28 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [RfC PATCH 0/3] option rom loading via fw_cfg
References: <1260985576-10736-1-git-send-email-kraxel@redhat.com>
	<37726A1E-223A-4C5D-ABC0-301A1D0E493C@suse.de>
In-Reply-To: <37726A1E-223A-4C5D-ABC0-301A1D0E493C@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

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