From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FfGgC-00026c-VI
	for qemu-devel@nongnu.org; Sun, 14 May 2006 09:30:41 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FfGgB-00026M-DV
	for qemu-devel@nongnu.org; Sun, 14 May 2006 09:30:40 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FfGgB-00026J-68
	for qemu-devel@nongnu.org; Sun, 14 May 2006 09:30:39 -0400
Received: from [212.227.126.171] (helo=moutng.kundenserver.de)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FfGiN-0002cm-3L
	for qemu-devel@nongnu.org; Sun, 14 May 2006 09:32:55 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by flubber.weilnetz.de (Postfix) with ESMTP id C41B5F2C46
	for <qemu-devel@nongnu.org>; Sun, 14 May 2006 15:30:22 +0200 (CEST)
Message-ID: <446730EE.8050008@mail.berlios.de>
Date: Sun, 14 May 2006 15:30:22 +0200
From: Stefan Weil <weil@mail.berlios.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel][PATCH]Get machine name from name of executable
References: <44670987.1030203@mail.berlios.de> <446718F4.9080400@bellard.org>
In-Reply-To: <446718F4.9080400@bellard.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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

Hi,

ok, I think this plan is a good one. It might even be possible to run 
several different machines by
starting a single QEMU emulation process. But you need some mechanism to 
tell QEMU which machine(s) to run.
Of course, you could add new command line options. MIPS, for example, 
could select endianness
automatically in user mode (from ELF format), but not in system mode 
when running a complete system
with a firmware loader. So you need some way to tell QEMU that this is a 
MIPS CPU with a certain kind
of endianness (the real CPU has a hardware input pin for this, we need 
something which replaces this
hardware input pin).

Did you think about using configuration files (XML, YAML, or any other 
format) with machine descriptions
(CPU, CPU variant, endianness, network hardware, serial ports, other 
hardware features which are
compiled into the code or configured via command line options today)?

Regards
Stefan

Fabrice Bellard schrieb:

> Hi,
>
> The long term plan for qemu is to have a single executable for all 
> machines. If you make a single executable for mips and mipsel, it is 
> better to select the endianness in the code of the machine itself when 
> initializing the CPU.
>
> Regards,
>
> Fabrice.