public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
* [PATCH] m68k: add ColdFire FPU support for the V4e ColdFire CPU's
@ 2011-11-03  5:54 gerg
  2011-11-03  5:54 ` gerg
  0 siblings, 1 reply; 7+ messages in thread
From: gerg @ 2011-11-03  5:54 UTC (permalink / raw)
  To: linux-m68k


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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2011-11-04  1:14 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox