From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ci20_defconfig: disable madd instructions to avoid FPU bug
Date: Sat, 22 Oct 2016 14:08:38 +0200 [thread overview]
Message-ID: <20161022140838.165b2fc0@free-electrons.com> (raw)
In-Reply-To: <d058213e-21f3-59e3-49ae-103d4fce6a8c@mind.be>
Hello,
On Fri, 21 Oct 2016 21:45:52 +0200, Arnout Vandecappelle wrote:
> > Ideally, we should mimic what we do on ARM, and only list in
> > "Target architecture variants" the cores and not the ISA. How many
> > vendors are doing MIPS cores, and how many cores are they doing?
>
> I believe that for MIPS, every vendor uses their own core, and that there is an
> almost one-to-one mapping between SoC family and core. AFAIU it's only the
> instruction set that is standardized. My gcc supports 74 cores... Do we really
> want to add all of these?
Well, did you count for ARM? There are also many many cores supported
in gcc. Admittedly probably not 74 cores, indeed.
> That said, now we already have a bit a mixed situation: we have a few
> processors and a few generic options in Config.in.mips. But I expect that
> Buildroot will often be used on SoCs where either Buildroot or GCC doesn't have
> a processor-specific option yet, so the generic ones will still be needed.
OK, fair enough. Then maybe they should be clearly separated by a
comment within the choice...endchoice block.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-10-22 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 12:24 [Buildroot] [PATCH] ci20_defconfig: disable madd instructions to avoid FPU bug Vicente Olivert Riera
2016-10-18 12:54 ` Thomas Petazzoni
2016-10-19 8:47 ` Vicente Olivert Riera
2016-10-19 9:31 ` Peter Korsgaard
2016-10-19 9:32 ` Thomas Petazzoni
2016-10-19 10:19 ` Vicente Olivert Riera
2016-10-21 19:45 ` Arnout Vandecappelle
2016-10-22 12:08 ` Thomas Petazzoni [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=20161022140838.165b2fc0@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox