From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NLDZn-00056h-DV for qemu-devel@nongnu.org; Thu, 17 Dec 2009 05:27:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NLDZi-00054b-1F for qemu-devel@nongnu.org; Thu, 17 Dec 2009 05:27:18 -0500 Received: from [199.232.76.173] (port=35539 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NLDZh-00054S-QU for qemu-devel@nongnu.org; Thu, 17 Dec 2009 05:27:13 -0500 Received: from cantor.suse.de ([195.135.220.2]:38332 helo=mx1.suse.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NLDZh-0000pZ-Ir for qemu-devel@nongnu.org; Thu, 17 Dec 2009 05:27:13 -0500 Message-ID: <4B2A077F.40308@suse.de> Date: Thu, 17 Dec 2009 11:27:11 +0100 From: Alexander Graf 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> <4B29FB24.9010106@redhat.com> In-Reply-To: <4B29FB24.9010106@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: "qemu-devel@nongnu.org" Gerd Hoffmann wrote: > On 12/17/09 00:47, Alexander Graf wrote: >> >> Am 16.12.2009 um 18:46 schrieb Gerd Hoffmann : >> >>> 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