From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LDMs1-0003D4-AV
	for qemu-devel@nongnu.org; Thu, 18 Dec 2008 12:41:09 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LDMrz-0003CI-Pe
	for qemu-devel@nongnu.org; Thu, 18 Dec 2008 12:41:08 -0500
Received: from [199.232.76.173] (port=48725 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LDMrz-0003C7-JB
	for qemu-devel@nongnu.org; Thu, 18 Dec 2008 12:41:07 -0500
Received: from mx2.redhat.com ([66.187.237.31]:43078)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <gleb@redhat.com>) id 1LDMrx-0005gO-20
	for qemu-devel@nongnu.org; Thu, 18 Dec 2008 12:41:07 -0500
Date: Thu, 18 Dec 2008 19:41:44 +0200
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] x86: Manage BIOS boot menu via command line
Message-ID: <20081218174144.GD7215@redhat.com>
References: <494A4A55.2090700@siemens.com>
	<200812181620.01572.paul@codesourcery.com>
	<494A7A46.7040300@codemonkey.ws> <494A80DE.6020601@siemens.com>
	<494A8704.6030102@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <494A8704.6030102@codemonkey.ws>
Reply-To: qemu-devel@nongnu.org
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: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org

On Thu, Dec 18, 2008 at 11:23:16AM -0600, Anthony Liguori wrote:
>> I'm open for the firmware config if you explain to me how state
>> information is supposed to be transfered from rombios32.c (where the
>> fw_cfg is evaluated) to some function in rombios.c. Tried this but found
>> nothing obvious.
>>   
>
> Gleb, could you comment here?  I'm obviously ignorant of the firmware  
> config code in the BIOS.  It seems like the right thing to use but if  
> it's all the current support is in 32-bit code, it may be difficult to  
> use that within the 16-bit code without rewriting it all.
>
Firmware config is accessed by inb/outw IO instructions so it should be
easy to do that from rombios.c. But it is possible to read the option
in rombios32.c and put it somewhere in unused space in 0x400 and check 
the value from rombios.c.

--
			Gleb.