From: Greg Ungerer <gerg@snapgear.com>
To: Finn Thain <fthain@telegraphics.com.au>
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:01:39 +1000 [thread overview]
Message-ID: <4EB23C53.8040709@snapgear.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1111031752060.2899@nippy.intranet>
Hi Finn,
On 03/11/11 16:53, Finn Thain wrote:
> On Thu, 3 Nov 2011, I wrote:
>
>> 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?
>
> Oops, I forgot about the compiler's optimiser...
Yeah, thats right. Most of the code here is optimized out currently.
It may be possible to have a single image boot on both m68k and
ColdFire. And where ever possible I am leaving the option open
in the code. But we have quite a few hurdles to jump over before
the code will actually be able to do it.
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
next prev parent reply other threads:[~2011-11-03 7:04 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 [this message]
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=4EB23C53.8040709@snapgear.com \
--to=gerg@snapgear.com \
--cc=fthain@telegraphics.com.au \
--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