From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] arch/mips: improve help text of NaN option
Date: Mon, 17 Jul 2017 14:56:13 +0200 [thread overview]
Message-ID: <20170717145613.3c7feb8a@windsurf> (raw)
In-Reply-To: <20170717122255.61795-1-Vincent.Riera@imgtec.com>
Hello,
On Mon, 17 Jul 2017 13:22:54 +0100, Vicente Olivert Riera wrote:
> diff --git a/arch/Config.in.mips b/arch/Config.in.mips
> index 7dd69659d..f2b352b0b 100644
> --- a/arch/Config.in.mips
> +++ b/arch/Config.in.mips
> @@ -169,7 +169,9 @@ choice
> depends on BR2_mips_32r5 || BR2_mips_64r5
> default BR2_MIPS_ENABLE_NAN_2008
> help
> - NaN encoding to be used
> + MIPS supports two different NaN encodings, legacy and 2008.
> + Information about MIPS NaN encodings can be found here:
> + https://sourceware.org/binutils/docs/as/MIPS-NaN-Encodings.html
Is it useful (and correct?) to say that the Linux kernel, built for
MIPS32r5, by default expect the 2008 NaN encoding?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-17 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 12:22 [Buildroot] [PATCH 1/2] arch/mips: improve help text of NaN option Vicente Olivert Riera
2017-07-17 12:22 ` [Buildroot] [PATCH 2/2] arch/mips: improve help text of FP32 mode option Vicente Olivert Riera
2017-07-17 12:56 ` Thomas Petazzoni [this message]
2017-07-17 16:57 ` [Buildroot] [PATCH 1/2] arch/mips: improve help text of NaN option Vicente Olivert Riera
2017-07-18 7:53 ` Thomas Petazzoni
2017-07-19 19:48 ` Thomas Petazzoni
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=20170717145613.3c7feb8a@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.