All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] arch/arm: Add Cortex-a53 CPU
Date: Fri, 19 Aug 2016 10:54:22 -0700	[thread overview]
Message-ID: <5F8C494A-03CF-46AC-B85D-107643848CD1@gmail.com> (raw)
In-Reply-To: <20160819194931.072912e5@free-electrons.com>


> On Aug 19, 2016, at 10:49 AM, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> 
> Hello,
> 
> On Fri, 19 Aug 2016 10:47:05 -0700, Khem Raj wrote:
> 
>>> 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.
>> 
>> 64bit kernel with 32bit userspace is most common usecase as of now for
>> a53 that I see. so you need some sort of multilib.
> 
> I think on RPi3 they use a 32 bit kernel and 32 bit userspace, which
> probably is what Matt was targeting. But I'd like to hear from Matt's
> use case first.

rpi3 is 32bit all the way, so this patch is fine for that case.
> 
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160819/15633324/attachment.asc>

  reply	other threads:[~2016-08-19 17:54 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
2016-08-19 17:47   ` Khem Raj
2016-08-19 17:49     ` Thomas Petazzoni
2016-08-19 17:54       ` Khem Raj [this message]
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=5F8C494A-03CF-46AC-B85D-107643848CD1@gmail.com \
    --to=raj.khem@gmail.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.