All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] arch/arm: Add Cortex-a53 CPU
Date: Fri, 19 Aug 2016 15:32:22 +0200	[thread overview]
Message-ID: <20160819133222.GO22524@waldemar-brodkorb.de> (raw)
In-Reply-To: <20160819100320.1d2609bd@free-electrons.com>

Hi Thomas,
Thomas Petazzoni wrote,

> Hello,
> 
> On Fri, 19 Aug 2016 10:07:04 +1000, Matt Flax wrote:
> > Adds the Cortex-a53 CPU to the target architecture variant choice. This sets
> > the toolchain to use cortex-a53 as the target. The effect is that various
> > cortex-a53 tunings are enabled for the compilation of packages.
> > 
> > Signed-off-by: Matt Flax <flatmax@flatmax.org>
> 
> The A53 is an ARM64 CPU, so it should rather be added to
> Config.in.aarch64 (in which we don't yet have a CPU selection, but that
> can be added).
> 
> Or are you building a 32 bits ARM system for a Cortex-A53 ? In that
> case, adding it to Config.in.arm would be OK, but it's a bit annoying
> that we would have to duplicate many ARM CPUs between Config.in.arm and
> Config.in.aarch64.

The new rpi3 can be compiled with optimization for cortex-a53 in ARM
32 bit mode. The aarch64 port for rpi3 isn't complete. So this might
be a use case. I fixed one issue in uCLibc-ng in the past to allow
cortex-a53 optimized builds.

best regards
 Waldemar

  reply	other threads:[~2016-08-19 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  0:07 [Buildroot] [PATCH 1/1] arch/arm: Add Cortex-a53 CPU Matt Flax
2016-08-19  8:03 ` Thomas Petazzoni
2016-08-19 13:32   ` Waldemar Brodkorb [this message]
2016-08-19 17:47   ` Khem Raj
2016-08-19 17:49     ` Thomas Petazzoni
2016-08-19 17:54       ` Khem Raj
2016-08-20  4:01         ` Matt Flax

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=20160819133222.GO22524@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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.