From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NGYWX-0003VJ-Fz
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 08:48:41 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NGYWS-0003Na-AG
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 08:48:40 -0500
Received: from [199.232.76.173] (port=44607 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NGYWR-0003NA-VR
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 08:48:36 -0500
Received: from mail-yx0-f188.google.com ([209.85.210.188]:36444)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1NGYWR-0003rg-Ur
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 08:48:36 -0500
Received: by yxe26 with SMTP id 26so2207336yxe.4
	for <qemu-devel@nongnu.org>; Fri, 04 Dec 2009 05:48:35 -0800 (PST)
Message-ID: <4B19132F.2080205@codemonkey.ws>
Date: Fri, 04 Dec 2009 07:48:31 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
References: <1259922793-20433-1-git-send-email-agraf@suse.de>
In-Reply-To: <1259922793-20433-1-git-send-email-agraf@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [PATCH v2] [0.12] Map BIOS f-segment as RAM,
	not as ROM
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: Gleb Natapov <gleb@redhat.com>, Kevin O'Connor <kevin@koconnor.net>, qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>, Sebastian Herbszt <herbszt@gmx.de>

Alexander Graf wrote:
> SeaBIOS needs to write to the f-segment. So it needs to have some way to set
> that from read-only to read-write, write in it and when it's done set it to
> read-only again.
>
> On PCI we have a mechanism for that. The ISA machine does not though. To stay
> regression free and happily enable users to continue using the -M isapc machine
> let's just map it as RAM. The BIOS on PCI will set it to r/o later either way.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
>   

Thanks Alex.  Figuring out what to do here has been on my todo and this 
seems like a reasonable solution.

Regards,

Anthony Liguori