All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARM: Adding Maverick FPU support
Date: Mon, 07 Feb 2005 13:32:04 +0100	[thread overview]
Message-ID: <42075FC4.70700@bellard.org> (raw)
In-Reply-To: <200502042200.32185.paul@codesourcery.com>

Paul Brook wrote:
> On Friday 04 February 2005 19:08, Jason McMullan wrote:
> 
>>So, I'm working on an emulation environment for the Cirrus Logic EP93xx
>>processors with the Maverick Crunch(tm) FPUs.
>>
>>What files do I need to touch to add support for these instructions?
> 
> 
> At minimum target-arm/op.c, target-arm/translate.c, and target-arm/cpu.h.
> 
> Note that that FPA is implemented differently. I uses the same emulator as the 
> linux kernel, hooked up to the undefined instruction interrupt. I wouldn't 
> advise doing this as performance is really awful. It's approximately 2x 
> slower than target soft-float, and I guess about 20x slower than a native 
> implementation.

Just to give more information, the idea was not to integrate the FPA 
emulation in the CPU itself because I believed it was mostly implemented 
as a software FPU. The real directory of FPA should be 
qemu/linux-user/arm/nwfpe and _not_ qemu/target-arm/nwfpe. I left it in 
target-arm because of the CVS legacy...

Now if real ARM FPUs are implemented, I agree they should go in op.c and 
translate.c (an helper.c can be added too). There must be a way to 
disable it so that the exact emulated ARM CPU core can be selected with 
a command line option.

Fabrice.

  reply	other threads:[~2005-02-07 12:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 19:08 [Qemu-devel] ARM: Adding Maverick FPU support Jason McMullan
2005-02-04 22:00 ` Paul Brook
2005-02-07 12:32   ` Fabrice Bellard [this message]
2005-02-07 12:55     ` Lennert Buytenhek

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=42075FC4.70700@bellard.org \
    --to=fabrice@bellard.org \
    --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.