From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KdQy8-0004w5-HF
	for qemu-devel@nongnu.org; Wed, 10 Sep 2008 10:46:56 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KdQy7-0004vN-1t
	for qemu-devel@nongnu.org; Wed, 10 Sep 2008 10:46:56 -0400
Received: from [199.232.76.173] (port=44561 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KdQy6-0004vJ-Nl
	for qemu-devel@nongnu.org; Wed, 10 Sep 2008 10:46:54 -0400
Received: from mail.codesourcery.com ([65.74.133.4]:36566)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1KdQy6-0004Ta-9b
	for qemu-devel@nongnu.org; Wed, 10 Sep 2008 10:46:54 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [Patch] Ali Chipset support for PC [+ questions
	about alpha-softmmu target]
Date: Wed, 10 Sep 2008 15:46:49 +0100
References: <1220975614.29130.86.camel@nibbler.dlib.indiana.edu>
	<1221052296.10782.23.camel@nibbler.dlib.indiana.edu>
	<79A514F4-8DF0-4D20-A74D-BBA41924AE24@adacore.com>
In-Reply-To: <79A514F4-8DF0-4D20-A74D-BBA41924AE24@adacore.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200809101546.50375.paul@codesourcery.com>
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: qemu-devel@nongnu.org
Cc: Tristan Gingold <gingold@adacore.com>

> So if you get the SRM decompressed from es40, you can start to work
> on the softmmu emulation.

Does linux actually use the bios at all once it's loaded[1]?
If not the simplest solution may be to load the kernel directly, and ignore 
the machine firmware.

[1] On Open Firmware based systems the kernel tends to use the firmware 
interface for doing initial machine setup and hardware probing.  On most 
other systems there's no real interaction between the bootloader and the 
kernel.  You just load the kernel into ram and set it going..

Paul