From: <gerg@snapgear.com>
To: linux-m68k@vger.kernel.org
Subject: [PATCH] m68k: add ColdFire FPU support for the V4e ColdFire CPU's
Date: Thu, 3 Nov 2011 15:54:04 +1000 [thread overview]
Message-ID: <1320299645-9105-1-git-send-email-gerg@snapgear.com> (raw)
Hi All,
Here is an improved patch set for FPU support on the ColdFire V4e.
Much cleaner than the ifdefery for this in the ColdFire/MMU patch
set I sent recently. (So of course this replaces that patch).
Does anyone know why some of the code for using fsave/frestore is
surrounded by ".chip" directives and others are not? For example
in arch/m68k/kernel/process_mm.c you will find this:
__asm__ volatile (".chip 68k/68881\n\t"
"frestore %0\n\t"
".chip 68k" : : "m" (*sc->sc_fpstate));
and you will also find this:
asm volatile ("frestore %0" : : "m" (p->thread.fpstate[0]));
I can use the second form directly on ColdFire, but not the first...
Regards
Greg
next reply other threads:[~2011-11-03 5:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 5:54 gerg [this message]
2011-11-03 5:54 ` [PATCH] m68k: add ColdFire FPU support for the V4e ColdFire CPU's 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
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=1320299645-9105-1-git-send-email-gerg@snapgear.com \
--to=gerg@snapgear.com \
--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