From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCE3h-0007eu-Ks for qemu-devel@nongnu.org; Sun, 22 Nov 2009 10:09:01 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCE3d-0007eB-73 for qemu-devel@nongnu.org; Sun, 22 Nov 2009 10:09:01 -0500 Received: from [199.232.76.173] (port=42755 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCE3d-0007e7-0V for qemu-devel@nongnu.org; Sun, 22 Nov 2009 10:08:57 -0500 Received: from mail.gmx.net ([213.165.64.20]:44714) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1NCE3c-000323-7W for qemu-devel@nongnu.org; Sun, 22 Nov 2009 10:08:56 -0500 Message-ID: From: "Sebastian Herbszt" References: <20091120225113.GD24539@morn.localdomain> <20091122123503.GH3193@redhat.com> In-Reply-To: <20091122123503.GH3193@redhat.com> Subject: Re: [Qemu-devel] Re: POST failure (loop) with isapc and seabios Date: Sun, 22 Nov 2009 16:07:56 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov , Kevin O'Connor Cc: qemu-devel@nongnu.org Gleb Natapov wrote: > On Fri, Nov 20, 2009 at 05:51:13PM -0500, Kevin O'Connor wrote: >> On Thu, Nov 19, 2009 at 10:30:20PM +0100, Sebastian Herbszt wrote: >> > i386-softmmu/qemu -M isapc -bios pc-bios/bios.bin >> >> Thanks for reporting this. >> >> After compiling seabios with CONFIG_DEBUG_SERIAL set in src/config.h >> and running: >> >> qemu -M isapc -serial file:foo >> >> I see: >> >> Unable to unlock ram - bridge not found >> >> SeaBIOS stores global variables in the f-segment. This greatly >> simplifies the code, but it does require the ability to write to the >> f-segment. Since the f-segment can't be unlocked in "isapc" mode, the >> boot fails. >> >> I'm not really sure what to do about this. Maybe some kind of non-pci >> method of unlocking the f-segment could be implemented. >> >> Anthony, what do you think? >> > May be make qemu to map it writable if isapc is specified. I don't think keeping the segment writable after POST is a good idea. - Sebastian