From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH 1/2] m68k: make support for FPU hardware configurable
Date: Tue, 21 Feb 2012 15:56:30 +1000 [thread overview]
Message-ID: <4F43320E.4000900@snapgear.com> (raw)
In-Reply-To: <CAMuHMdVnOsxKCvUtCbwb_RqKp8L7HLfb4jEO8_Hnewvry+33nQ@mail.gmail.com>
Hi Geert,
On 19/02/12 20:17, Geert Uytterhoeven wrote:
> On Fri, Feb 10, 2012 at 07:14,<gerg@snapgear.com> wrote:
>> The classic m68k code has always supported an FPU (although it may have
>> been a software emulated one). The non-MMU m68k code has never supported FPU
>> hardware. To help in merging common code create a configation setting that
>> signifies if we are builing in FPU support or not.
>>
>> This switch, CONFIG_FPU, is set as per the current use cases. So it is
>> always enabled if CONFIG_MMU is set, and disabled otherwise. With a little
>> extra code it will be possible to disable it on the classic m68k platforms
>> as well, and to enable it on non-MMU platforms that do have hardware FPU.
>>
>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>
> Acked-by: Geert Uytterhoeven<geert@linux-m68k.org>
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
prev parent reply other threads:[~2012-02-21 6:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 6:14 [PATCH 1/2] m68k: make support for FPU hardware configurable gerg
2012-02-10 6:14 ` [PATCH 2/2] m68k: merge the MMU and non-MMU versions of process.c gerg
2012-02-19 10:18 ` Geert Uytterhoeven
2012-02-19 10:17 ` [PATCH 1/2] m68k: make support for FPU hardware configurable Geert Uytterhoeven
2012-02-21 5:56 ` 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=4F43320E.4000900@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.