qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] arm: basic support for ARMv4/ARMv4T emulation
Date: Mon, 11 Apr 2011 19:18:20 +0400	[thread overview]
Message-ID: <BANLkTinLhdQD2fDFKhaKN7Qo_7DiVJT-Zg@mail.gmail.com> (raw)
In-Reply-To: <201104101424.22093.marek.vasut@gmail.com>

Hi,

On 4/10/11, Marek Vasut <marek.vasut@gmail.com> wrote:
> On Monday 04 April 2011 15:38:44 Dmitry Eremin-Solenikov wrote:
>> Currently target-arm/ assumes at least ARMv5 core. Add support for
>> handling also ARMv4/ARMv4T. This changes the following instructions:
>>
>> BX(v4T and later)
>>
>> BKPT, BLX, CDP2, CLZ, LDC2, LDRD, MCRR, MCRR2, MRRC, MCRR, MRC2, MRRC,
>> MRRC2, PLD QADD, QDADD, QDSUB, QSUB, STRD, SMLAxy, SMLALxy, SMLAWxy,
>> SMULxy, SMULWxy, STC2 (v5 and later)
>>
>> All instructions that are "v5TE and later" are also bound to just v5, as
>> that's how it was before.
>>
>> This patch doesn _not_ include disabling of cp15 access and base-updated
>> data abort model (that will be required to emulate chips based on a
>> ARM7TDMI), because:
>> * no ARM7TDMI chips are currently emulated (or planned)
>
> Hi,
>
> this will come handy as I plan to add support for certain arm7tdmi chip
> (forward
> port at91sam7 patchset)

Please be sure to check for the base-updated/base-restored part of the original
patch as I'm nearly sure that it will be required for your chips.

-- 
With best wishes
Dmitry

  reply	other threads:[~2011-04-11 15:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 13:38 [Qemu-devel] [PATCH 0/3] StrongARM/collie support Dmitry Eremin-Solenikov
2011-04-04 13:38 ` [Qemu-devel] [PATCH 1/3] arm: basic support for ARMv4/ARMv4T emulation Dmitry Eremin-Solenikov
2011-04-06 13:56   ` Peter Maydell
2011-04-06 17:41     ` Dmitry Eremin-Solenikov
2011-04-06 17:50       ` Peter Maydell
2011-04-10 11:25   ` Aurelien Jarno
2011-04-10 12:24   ` Marek Vasut
2011-04-11 15:18     ` Dmitry Eremin-Solenikov [this message]
2011-04-04 13:38 ` [Qemu-devel] [PATCH 2/3] Implement basic part of SA-1110/SA-1100 Dmitry Eremin-Solenikov
2011-04-10 11:40   ` Aurelien Jarno
2011-04-04 13:38 ` [Qemu-devel] [PATCH 3/3] Basic implementation of Sharp Zaurus SL-5500 collie PDA Dmitry Eremin-Solenikov
2011-04-10 11:41   ` Aurelien Jarno
  -- strict thread matches above, loose matches on Subject: below --
2011-04-04 12:15 [Qemu-devel] [PATCH 1/3] arm: basic support for ARMv4/ARMv4T emulation Dmitry Eremin-Solenikov
2011-03-30 11:41 Dmitry Eremin-Solenikov
2011-03-30 16:12 ` Peter Maydell
2011-03-30 23:27   ` Dmitry Eremin-Solenikov
2011-04-02 15:25     ` Dmitry Eremin-Solenikov
2011-04-04 11:21       ` Peter Maydell
2011-03-29 16:58 Dmitry Eremin-Solenikov
2011-03-29 17:56 ` Peter Maydell
2011-03-24 22:07 Dmitry Eremin-Solenikov
2011-03-25 15:00 ` Peter Maydell
2011-03-26 17:23   ` Dmitry Eremin-Solenikov
2011-03-26 18:08     ` Peter Maydell
2011-03-26 22:31       ` Dmitry Eremin-Solenikov
2011-03-26 23:41 ` Peter Maydell
2011-03-29 16:47   ` Dmitry Eremin-Solenikov
2011-03-24 10:22 Dmitry Eremin-Solenikov

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=BANLkTinLhdQD2fDFKhaKN7Qo_7DiVJT-Zg@mail.gmail.com \
    --to=dbaryshkov@gmail.com \
    --cc=marek.vasut@gmail.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).