public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Vered Zvi <veredz@elta.co.il>
To: Bryan Hundven <bryanhundven@gmail.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: RE: toolchain for NXP's LS1021A (cortex-A7)
Date: Wed, 23 Nov 2016 09:51:00 -0000	[thread overview]
Message-ID: <1EFFBDE6584C794F8A0ADF2CAC8D60E09F8CBA82@eltidex2.elta.co.il> (raw)
In-Reply-To: <7A273260-2427-44F3-A64F-11652061E089@gmail.com>

Hi Bryan,

Thank you very much !

Best regards,
Z.V

________________________________________
From: Bryan Hundven [bryanhundven@gmail.com]
Sent: Wednesday, November 23, 2016 6:53 AM
To: Vered Zvi
Cc: crossgcc@sourceware.org
Subject: Re: toolchain for NXP's LS1021A (cortex-A7)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Vered,

On Nov 22, 2016, at 7:26 PM, Vered Zvi <veredz@elta.co.il> wrote:

Hello,

I'm using NXP's LS1021A (ARM cortex-A7)

I'm using crosstool-ng 1.22.0 to create a toolchain in order to compile u-boot, linux.

What item in the list-samples should I choose ?

arm-bare_newlib_cortex_m3_nommu-eabi
arm-cortex_a15-linux-gnueabi
arm-cortexa5-linux-uclibcgnueabihf

Considering that the processor is a Cortex A7, you could take any one of the samples that are `A<Whatever>` and change the gcc configure options appropriately to optimize for A7. The samples we have in git repository are there to try to keep a diverse build set that we built on travis-ci (when that worked…). A7 just wasn’t added, I guess...

arm-cortex_a8-linux-gnueabi
arm-cortexa9_neon-linux-gnueabihf
armeb-unknown-eabi
armeb-unknown-linux-gnueabi
armeb-unknown-linux-uclibcgnueabi
arm-unknown-eabi
arm-unknown-linux-gnueabi
arm-unknown-linux-musleabi
arm-unknown-linux-uclibcgnueabi
arm-unknown-linux-uclibcgnueabihf
armv6-rpi-linux-gnueabi
armv7-rpi2-linux-gnueabihf

Thank you,
Z.V
The information contained in this communication is proprietary to Israel Aerospace Industries Ltd. and/or third parties, may contain confidential or privileged information, and is intended only for the use of the intended addressee thereof. If you are not the intended addressee, please be aware that any use, disclosure, distribution and/or copying of this communication is strictly prohibited. If you receive this communication in error, please notify the sender immediately and delete it from your computer.

The information I provided is in the public domain, and conflicts with the footer of your email. Please remove your internal signature when conversing in the open-source world. Thanks!

- -Bryan
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJYNSC9AAoJEMrXyPw1uHHRzGAH/iKMXKx5R3Ouat8TusqqpyAZ
IiLugYQJ6EEtqM3TKvDTZleH36aPgkEuobtdeus7zBSagX26SZEVhKE3Un3JrDbs
Vv1/YWgtgfaODatI8+8AhjABIcNTxptpjyQn0u6M2mNeGUlkedsRHZk0apgi+3Lg
MhJDoyOoabfXndXVV17e2BuVQXKoKuoLLeea644K56aU7+BQlI7d9kO5GEpadFUT
ENLgFOjLeXkr2qBZu3zSINPI+SoVlGMfRRULJZfT0newSw0KMqIGVgXS5jCBWMSC
wvXWLWDABSzbMfo9RK2gRpRQLLK10Od961vc8Hv1jDwwztesyz3A8ssT5SM1LVM=
=I6p0
-----END PGP SIGNATURE-----


This Email and the attachments were emulated by Check Point ThreatEmulation Service.
The information contained in this communication is proprietary to Israel Aerospace Industries Ltd. and/or third parties, may contain confidential or privileged information, and is intended only for the use of the intended addressee thereof. If you are not the intended addressee, please be aware that any use, disclosure, distribution and/or copying of this communication is strictly prohibited. If you receive this communication in error, please notify the sender immediately and delete it from your computer.


--
For unsubscribe information see http://sourceware.org/lists.html#faq

      reply	other threads:[~2016-11-23  9:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23  3:27 Vered Zvi
2016-11-23  4:53 ` Bryan Hundven
2016-11-23  9:51   ` Vered Zvi [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=1EFFBDE6584C794F8A0ADF2CAC8D60E09F8CBA82@eltidex2.elta.co.il \
    --to=veredz@elta.co.il \
    --cc=bryanhundven@gmail.com \
    --cc=crossgcc@sourceware.org \
    /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).