qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Missing ARMv6 instructions?
Date: Mon, 3 Apr 2006 13:42:42 +0100	[thread overview]
Message-ID: <200604031342.44774.paul@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0604030840070.419@silence.gardas.net>

> IMHO majority of embedded devices is still ARM7TDMI based and this
> instruction set (ARMv4 IIRC) should be emulated well in Qemu.

Depends which market segments you're aiming at.

If you're aiming at well established legacy or cheap, low-end hardware then 
yes armv4t is fine.

If you want to use qemu for development/prototyping of new products then you 
need an emulator that knows about modern systems, not something two 
generations out of date.

Paul

      parent reply	other threads:[~2006-04-03 12:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 12:33 [Qemu-devel] Missing ARMv6 instructions? Wolfgang Schildbach
2006-03-29 14:39 ` Paul Brook
2006-03-29 16:00   ` Wolfgang Schildbach
2006-03-29 20:39     ` Jamie Lokier
2006-03-29 22:01       ` Paul Brook
2006-03-29 22:36         ` John Hogerhuis
2006-03-29 22:37         ` Jamie Lokier
2006-03-30  9:22         ` Wolfgang Schildbach
2006-03-30 14:30           ` Jamie Lokier
2006-03-30 15:25             ` Lennert Buytenhek
2006-03-30 15:50               ` Paul Brook
2006-03-29 20:40     ` Jamie Lokier
2006-04-01 19:51     ` Chris Wilson
2006-04-01 20:06       ` Jonas Maebe
2006-04-02  1:26         ` Kevin F. Quinn
2006-04-02 16:32       ` Jamie Lokier
2006-04-02 16:42         ` Chris Wilson
2006-04-04 19:42           ` Daniel Jacobowitz
2006-04-05 14:41           ` Thiemo Seufer
2006-04-03  6:42         ` Karel Gardas
2006-04-03  7:00           ` M. Warner Losh
2006-04-03 12:42           ` Paul Brook [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=200604031342.44774.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).