From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKYTJ-0002vY-Qy for qemu-devel@nongnu.org; Tue, 15 Dec 2009 09:33:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKYTE-0002u0-04 for qemu-devel@nongnu.org; Tue, 15 Dec 2009 09:33:52 -0500 Received: from [199.232.76.173] (port=58777 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKYTD-0002ti-GI for qemu-devel@nongnu.org; Tue, 15 Dec 2009 09:33:47 -0500 Received: from mx1.redhat.com ([209.132.183.28]:18315) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKYTD-0001at-6E for qemu-devel@nongnu.org; Tue, 15 Dec 2009 09:33:47 -0500 Message-ID: <4B279E47.80109@redhat.com> Date: Tue, 15 Dec 2009 16:33:43 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [SeaBIOS] Proper support for PCI-based option rom loading (was Re: [Qemu-devel] Re: qdev property bug?) References: <4B26931E.4000101@codemonkey.ws> <20091214194210.GB6150@redhat.com> <4B269933.3010906@codemonkey.ws> <20091214202019.GF6150@redhat.com> <4B26A0DE.5000304@redhat.com> <20091214203428.GI6150@redhat.com> <20091214203603.GJ6150@redhat.com> <4B26A3B2.2030006@codemonkey.ws> <20091214205141.GC6398@redhat.com> <4B26F678.4010603@codemonkey.ws> <20091215043454.GD22611@morn.localdomain> <4B278BE9.3010900@codemonkey.ws> <4B279B24.1090004@codemonkey.ws> In-Reply-To: <4B279B24.1090004@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin O'Connor , seabios@seabios.org, qemu-devel@nongnu.org On 12/15/2009 04:20 PM, Anthony Liguori wrote: > Anthony Liguori wrote: >> >> The bios gets mapped in 0xe0000 .. 0x100000 so if SeaBIOS fills the >> 0xc0000-0xf0000 space it will write over half of the bios. > > I'm a little confused by this. SeaBIOS seems to assume that it only > has to deal with the 0xf0000 .. 0x100000 space as the bios which is > certainly true (i don't think there's anything special about the > 0xe0000 .. 0xf0000 region). > > I'm not sure why we load the 128K worth of bios instead of just > loading 64K. > bochs bios required all 128kB, so this is probably a leftover. -- error compiling committee.c: too many arguments to function