From: Bryan Hundven <bryanhundven@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: crossgcc@sourceware.org
Subject: Re: [crosstool-ng/crosstool-ng] bc9ed3: Adds Raspberry Pi 3 sample config
Date: Fri, 11 Mar 2016 02:06:00 -0000 [thread overview]
Message-ID: <F77689F4-8537-4BDA-8F52-23FCC887BD13@gmail.com> (raw)
In-Reply-To: <20160310222005.7bf64c63@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
> On Mar 10, 2016, at 1:20 PM, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
>
> Hello,
>
> On Wed, 02 Mar 2016 12:11:45 -0800, Bryan Hundven wrote:
>
>> Changed paths:
>> A samples/armv8-rpi3-linux-gnueabihf/crosstool.config
>> A samples/armv8-rpi3-linux-gnueabihf/reported.by
>
> I think it is not a good idea to have a configuration named after a
> board, as the discussion generated around this addition shows.
>
> Indeed, an ARMv8 processor can run both in 32 bits mode or 64 bits mode
> depending on the use cases. So a single board like the RPi3 can
> require the use of either an ARM toolchain, or an AArch64 toolchain.
>
> So, I think you should stick to configurations for processor cores, not
> boards. So:
>
> arm-cortex-a15
> arm-cortex-a7
> aarch64-cortex-a53
> aarch64-cortex-a72
> ...
>
> Then, a RPi3 user can chose either an arm-* toolchain or an aarch64-*
> toolchain depending on what he wants to do.
I can agree with that. I’ll look into renaming the samples soon!
Cheers,
-Bryan
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
prev parent reply other threads:[~2016-03-11 2:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 20:11 Bryan Hundven
2016-03-02 23:51 ` Mike Ray
2016-03-03 0:23 ` Bryan Hundven
2016-03-03 0:28 ` Stefan Hallas Mulvad
2016-03-03 6:23 ` Mike Ray
2016-03-03 12:45 ` Bryan Hundven
2016-03-03 15:19 ` Bryan Hundven
2016-03-03 15:52 ` Mike Ray
2016-03-03 15:58 ` Bryan Hundven
2016-03-03 0:25 ` Stefan Hallas Mulvad
2016-03-10 21:20 ` Thomas Petazzoni
2016-03-11 2:06 ` Bryan Hundven [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=F77689F4-8537-4BDA-8F52-23FCC887BD13@gmail.com \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=thomas.petazzoni@free-electrons.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).