Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 19 Oct 2016 11:32:29 +0200	[thread overview]
Message-ID: <20161019113229.02a9d8c3@free-electrons.com> (raw)
In-Reply-To: <68e76d80-a505-e029-941a-fe43d9780536@imgtec.com>

Hello,

On Wed, 19 Oct 2016 09:47:03 +0100, Vicente Olivert Riera wrote:

> We could add an Ingenic XBurst entry in the MIPS CPU selection, and then
> add that -mno-fused-madd option to the wrapper based on that selection.
> 
> If you are OK with that, please let me know and I'll cook the patch.

If I understand correctly:

 - JZ4780 is the SoC
 - XBurst is the core
 - MIPS32r2 is the ISA

So indeed, it makes sense to add an option for XBurst, in order to
mimic what we do on ARM.

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?

If you look at ARM, we have the following situation:

 - Freescale, TI, Atmel, Marvell, Qualcomm, Nvidia, etc. are doing SoCs
   They are way too many for Buildroot to have a list of them.

 - Very few vendors are doing cores. Most of the SoC vendors are using
   the cores from ARM. For example, we have ARM926, Cortex-A7, Cortex-A8,
   Cortex-A53, etc.

   Those are the ones that are listed in "Target Architecture Variant",
   and we use the selected option to know the ISA.

 - ISAs are ARMv4, ARMv5, ARMv6, ARMv7, ARMv8, with a few variants.

So having a similar model for MIPS would be ideal.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2016-10-19  9:32 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 [this message]
2016-10-19 10:19       ` Vicente Olivert Riera
2016-10-21 19:45       ` Arnout Vandecappelle
2016-10-22 12:08         ` 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=20161019113229.02a9d8c3@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