All of lore.kernel.org
 help / color / mirror / Atom feed
From: vibisreenivasan <vibi_sreenivasan@cms.com>
To: andrzej zaborowski <balrogg@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Can we run code for ARM920T core (at91rm9200) in qemu
Date: Mon, 05 Jan 2009 16:13:45 +0530	[thread overview]
Message-ID: <1231152225.10165.1.camel@localhost.localdomain> (raw)
In-Reply-To: <fb249edb0901032331l35b2c607jb88115c242b5981a@mail.gmail.com>

Thanks for the reply..
Any Idea about qemu support for ARM7TDMI core?Any one planning to
implement that?
regards
vibi sreenivasan

On Sun, 2009-01-04 at 08:31 +0100, andrzej zaborowski wrote:
> 2009/1/2 vibisreenivasan <vibi_sreenivasan@cms.com>:
> > hi Warner,
> >        Thanks for the fast response.
> >        Is there any one working on adding support for ARM920T core.
> >
> >        Can any one give me some points on how to add support for
> >        ARM920T core.
> 
> Most (all?) of the instructions ARM920T supports are in ARM926 too so
> most of the changes would be restricting the exisitng instruction set
> to generate faults on v5-only instructions.  If you don't care about
> the faults then mostly anything that runs on ARM920T will run in qemu
> as is.  The openmoko qemu tree emulates a cpu with an ARM920T core but
> without implementing the differences from arm926.
> 
> Cheers

  reply	other threads:[~2009-01-05 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01 11:02 [Qemu-devel] Can we run code for ARM920T core (at91rm9200) in qemu vibisreenivasan
2009-01-01 15:43 ` M. Warner Losh
2009-01-01 20:40   ` [Qemu-devel] " Måns Rullgård
2009-01-02  5:03   ` [Qemu-devel] " vibisreenivasan
2009-01-04  7:31     ` andrzej zaborowski
2009-01-05 10:43       ` vibisreenivasan [this message]
2009-01-05 10:51       ` [Qemu-devel] HOW TO ADD SUPPORT FOR A NEW arm926 based board (at91sam9260ek) vibisreenivasan

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=1231152225.10165.1.camel@localhost.localdomain \
    --to=vibi_sreenivasan@cms.com \
    --cc=balrogg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.