From: Finn Thain <fthain@telegraphics.com.au>
To: gerg@snapgear.com
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: Thu, 3 Nov 2011 17:44:24 +1100 (EST) [thread overview]
Message-ID: <alpine.LNX.2.00.1111031735050.2899@nippy.intranet> (raw)
In-Reply-To: <1320299645-9105-2-git-send-email-gerg@snapgear.com>
On Thu, 3 Nov 2011, gerg@snapgear.com wrote:
> #define FPSTATESIZE (96)
> #elif defined(CONFIG_M68KFPU_EMU)
> #define FPSTATESIZE (28)
> +#elif defined(CONFIG_COLDFIRE) && defined(CONFIG_MMU)
> +#define FPSTATESIZE (16)
...
> + if (CPU_IS_COLDFIRE) {
Is it actually possible to run the same kernel binary on CF and 680x0? If
not, shouldn't these run-time tests be compile-time #ifdefs?
Finn
next prev parent reply other threads:[~2011-11-03 6:44 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 [this message]
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=alpine.LNX.2.00.1111031735050.2899@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=gerg@snapgear.com \
--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