From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Support for Wireless MMX
Date: Fri, 18 Mar 2005 13:00:16 +0000 [thread overview]
Message-ID: <200503181300.16407.paul@codesourcery.com> (raw)
In-Reply-To: <001001c52ba8$b2b825c0$d3272dd5@bigclit>
On Friday 18 March 2005 10:53, Luca Piccarreta wrote:
> Hi all,
> after googling a lot I concluded (hopefully) that qemu is
> the only freely available solution for linux cross-toolchain
> (one armv5 and one iwmmxt toolchain).
The gdb simulator supports both armv5te and iwmmxt, though a small amount of
hacking may be required to enable iwmmxt properly.
> I might have made some mistakes, but it looks like there
> are still some problems with saturated operations (qadd)
> and support for Wireless MMX is lacking.
> Am I correct?
iWMMXt is not implemented.
Saturated operations should work, though I probably haven't tested them. If
you have examples that don't work, please let me/us know.
> Programs compiled by the armv5 toolchain seem to work
> correctly except for saturated operations, while programs
> compiled by the iwmmxt toolchain work only when no
> Wireless MMX is used and when normal ARMV5 shared
> libraries are used.
> Are both features in the future development plans?
> I saw Paul Brook post a lot of patches about ARM, so
> I'm quite confident...
I've no immediate interest in iWMMXt.
I do plan on adding support for newer arm architecture revisions, ie. armv6
and future revisions once they're public.
System emulation would be nice, but that's definitely a secondary priority for
me. It probably won''t happen until after armv6 is done because armv6
standardises a lot of the MMU and system coprocessor design.
Paul
next prev parent reply other threads:[~2005-03-18 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 10:53 [Qemu-devel] Support for Wireless MMX Luca Piccarreta
2005-03-18 13:00 ` Paul Brook [this message]
2005-03-18 14:11 ` Luca Piccarreta
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=200503181300.16407.paul@codesourcery.com \
--to=paul@codesourcery.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).