From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FfL7U-00008b-L2 for qemu-devel@nongnu.org; Sun, 14 May 2006 14:15:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FfL7U-00007V-2g for qemu-devel@nongnu.org; Sun, 14 May 2006 14:15:08 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FfL7T-00007G-SF for qemu-devel@nongnu.org; Sun, 14 May 2006 14:15:07 -0400 Received: from [84.96.92.60] (helo=Smtp.neuf.fr) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FfL9i-0007eY-OW for qemu-devel@nongnu.org; Sun, 14 May 2006 14:17:26 -0400 Received: from [86.73.70.56] by sp604001mt.gpm.neuf.ld (Sun Java System Messaging Server 6.2-5.05 (built Feb 16 2006)) with ESMTP id <0IZ900BLQOUGFTB0@sp604001mt.gpm.neuf.ld> for qemu-devel@nongnu.org; Sun, 14 May 2006 20:03:53 +0200 (CEST) Date: Sun, 14 May 2006 20:03:17 +0200 From: Fabrice Bellard Subject: Re: [Qemu-devel][PATCH]Get machine name from name of executable In-reply-to: <446730EE.8050008@mail.berlios.de> Message-id: <446770E5.4000601@bellard.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT References: <44670987.1030203@mail.berlios.de> <446718F4.9080400@bellard.org> <446730EE.8050008@mail.berlios.de> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I don't understand your problem : the '-M' option is used to select the machine. Your "ar7" machine must be added as a new machine. The endianness must be selected inside the machine code. If the machine can be launched with the two endiannesses, then you can just add two machines names. Fabrice. Stefan Weil wrote: > 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. > > > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > >