From: "Luca Piccarreta" <piccarre@elet.polimi.it>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Support for Wireless MMX
Date: Fri, 18 Mar 2005 11:53:19 +0100 [thread overview]
Message-ID: <001001c52ba8$b2b825c0$d3272dd5@bigclit> (raw)
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).
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?
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...
Thanks in advance.
Luca Piccarreta.
next reply other threads:[~2005-03-18 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 10:53 Luca Piccarreta [this message]
2005-03-18 13:00 ` [Qemu-devel] Support for Wireless MMX Paul Brook
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='001001c52ba8$b2b825c0$d3272dd5@bigclit' \
--to=piccarre@elet.polimi.it \
--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).