qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Domen Puncer <domen.puncer@ultra.si>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: MIPS little endian system emulation?
Date: Wed, 11 Jan 2006 13:11:57 +0100	[thread overview]
Message-ID: <20060111121157.GC4842@domen.ultra.si> (raw)
In-Reply-To: <20060111115610.GB4842@domen.ultra.si>

On 11/01/06 12:56 +0100, Domen Puncer wrote:
> Hi.
> 
> What would need to be done for qemu to support little endian system
> emulation?
> I tried changing kernel config, to "support" little endian, and it
> even builds it. When i try to boot it with qemu-system-mips it...
> well... doesn't do anything.
> 
> I'm guessing that I need something like qemu-system-mipsel?
> Any hints on how to easily (if that's possible) provide it?

Hah, crazy, I changed this, and it worked:

--- qemu-0.8.0/configure	2005-12-19 23:51:53.000000000 +0100
+++ qemu/configure	2006-01-11 12:59:38.000000000 +0100
@@ -229,7 +229,7 @@
 
 if test -z "$target_list" ; then
 # these targets are portable
-    target_list="i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu arm-softmmu"
+    target_list="i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu arm-softmmu mipsel-softmmu"
 # the following are Linux specific
     if [ "$linux" = "yes" ] ; then
         target_list="i386-user arm-user armeb-user sparc-user ppc-user mips-user mipsel-user $target_list"


Sorry for the noise.
	 
> 
> Thank you in advance.
> 
> 
> 	Domen

  reply	other threads:[~2006-01-11 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 11:56 [Qemu-devel] MIPS little endian system emulation? Domen Puncer
2006-01-11 12:11 ` Domen Puncer [this message]
2006-01-11 16:37   ` [Qemu-devel] " Johannes Schindelin
2006-01-12 21:26 ` [Qemu-devel] " Fabrice Bellard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060111121157.GC4842@domen.ultra.si \
    --to=domen.puncer@ultra.si \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).