public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] m68k: add ColdFire FPU support for the V4e ColdFire CPU's
Date: Fri, 4 Nov 2011 11:16:07 +1000	[thread overview]
Message-ID: <4EB33CD7.2070509@snapgear.com> (raw)
In-Reply-To: <CAMuHMdUCzjkGL_Z3ki9nNrreL_+hxa2dwLZZ+LLB250w4UfYNA@mail.gmail.com>

Hi Geert,

On 03/11/11 18:28, Geert Uytterhoeven wrote:
> On Thu, Nov 3, 2011 at 06:54,<gerg@snapgear.com>  wrote:
>> The ColdFire FPU is of course different to all previous 68k FP units. It is
>> close in operation to the 68060, but not completely compatible. The biggest
>> issue to deal with is that the ColdFire FPU multi-move instructions are
>> different. It does not support multi-moving the FP control registers, and
>> the multi-move of the FP data registers uses a different instruction
>> neumonic.
>
> mnemonic

Thanks!

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

      reply	other threads:[~2011-11-04  1:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03  5:54 [PATCH] m68k: add ColdFire FPU support for the V4e ColdFire CPU's gerg
2011-11-03  5:54 ` gerg
2011-11-03  6:44   ` Finn Thain
2011-11-03  6:53     ` Finn Thain
2011-11-03  7:01       ` Greg Ungerer
2011-11-03  8:28   ` Geert Uytterhoeven
2011-11-04  1:16     ` Greg Ungerer [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=4EB33CD7.2070509@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.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