From: Dirk Behme <dirk.behme@googlemail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH][MIPS]
Date: Tue, 02 May 2006 18:14:29 +0200 [thread overview]
Message-ID: <44578565.1010704@gmail.com> (raw)
In-Reply-To: <173101c66de0$e01c97f0$e90d11ac@spb.in.rosprint.ru>
Alexander Voropay wrote:
> The current CVS QEMU Makefile builds "qemu-system-mips"
> binary which really emulates a little-endian system and should be
> renamed to the "qemu-system-mipsel"
With configure --target-list you can select mips-softmmu or
mipsel-softmmu. So I think it's a good idea to extend build
system to generate
mips-softmmu -> qemu-system-mips (big endian)
mipsel-softmmu -> qemu-system-mipsel (little endian)
Has anybody a patch for this?
> Is it possible to build _both_ "qemu-system-mips*" for
LE and BE support
> like userspace does ?
I don't think so at the moment. I'm not sure what happens if
both (little and big endian) targets are selected by configure.
Dirk
prev parent reply other threads:[~2006-05-02 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 14:26 [Qemu-devel] [PATCH][MIPS] FPU support for MIPS Marius Groeger
2006-04-26 22:17 ` Fabrice Bellard
2006-04-27 10:22 ` Marius Groeger
2006-05-02 12:06 ` [Qemu-devel] [PATCH][MIPS] Alexander Voropay
2006-05-02 16:14 ` Dirk Behme [this message]
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=44578565.1010704@gmail.com \
--to=dirk.behme@googlemail.com \
--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).