From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Jonas Gorski <jogo@openwrt.org>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Ralf Baechle <ralf@linux-mips.org>,
MIPS Mailing List <linux-mips@linux-mips.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MIPS: Replace CONFIG_MIPS64 and CONFIG_MIPS32_R2
Date: Thu, 10 Apr 2014 00:03:14 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.11.1404092356500.29561@eddie.linux-mips.org> (raw)
In-Reply-To: <CAOiHx=mi3sW7C0ZGwAhobRryikMs=Hj0UL19ENuUMECqk0EW5g@mail.gmail.com>
On Sun, 9 Feb 2014, Jonas Gorski wrote:
> While I agree about the CONFIG_MIPS64 => CONFIG_64BIT replacement, I
> wonder if CONFIG_MIPS32_R2 shouldn't rather be CONFIG_CPU_MIPSR2
> (maybe even the existing CONFIG_CPU_MIPS32_R2 are wrong here).
Absolutely. You should be able to build a 32-bit kernel (32BIT) for a
MIPS64r2 processor (CPU_MIPS64_R2) and use the FP64 feature.
Maciej
prev parent reply other threads:[~2014-04-09 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 13:32 [PATCH] MIPS: Replace CONFIG_MIPS64 and CONFIG_MIPS32_R2 Paul Bolle
2014-02-09 16:26 ` Jonas Gorski
2014-02-09 19:45 ` Aaro Koskinen
2014-02-15 14:45 ` Huacai Chen
2014-04-09 23:03 ` Maciej W. Rozycki [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=alpine.LFD.2.11.1404092356500.29561@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=jogo@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=pebolle@tiscali.nl \
--cc=ralf@linux-mips.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