From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] package/arm-gnu-a-toolchain: new package
Date: Fri, 14 Feb 2020 05:19:25 +0100 [thread overview]
Message-ID: <20200214051925.1d3b6cc3@windsurf> (raw)
In-Reply-To: <CAM+7aWuyvgf=ZjzxW+OAs+XpzT3yf+iru8JF7n+wQNAJLGg31Q@mail.gmail.com>
On Thu, 13 Feb 2020 15:31:59 +0530
Sunil Kumar Mahesh <sunil@amarulasolutions.com> wrote:
> One of the requirements to build ATF is to have Baremetal GNU GCC tools.
> This is stated in
> ATF documentation (ATF/docs/getting_started/user-guide.rst - section Tools)
No, the problem is not to have access to baremetal GC tools. On most
platforms we built ATF with a non-bare metal toolchain, and this works
just fine.
What justifies adding this toolchain is that the target platform is
ARM64, but ATF needs to be built bits of code for some ARM32
co-processor, and you can't build ARM32 code with an ARM64 toolchain.
Since all we need for ARM32 is to build bare-metal code, we use a
bare-metal ARM32 toolchain for that. But everything else in ATF will be
built by the regular non-bare-metal ARM64 toolchain built by Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-14 4:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 5:52 [Buildroot] [PATCH 0/4] Fix ATF v2.2 build for rk3399, add roc-rk3399-pc board sunil at amarulasolutions.com
2020-02-13 5:52 ` [Buildroot] [PATCH 1/4] boot/arm-trusted-firmware: Disable bin copy for rk3399 sunil at amarulasolutions.com
2020-02-13 7:23 ` Sergey Matyukevich
2020-02-13 8:06 ` Jagan Teki
2020-02-14 4:20 ` Thomas Petazzoni
2020-02-14 6:55 ` Jagan Teki
2020-02-14 7:26 ` Thomas Petazzoni
2020-02-14 7:34 ` Jagan Teki
2020-02-14 10:57 ` Sunil Kumar Mahesh
2020-02-14 12:33 ` Sunil Kumar Mahesh
2020-02-13 5:52 ` [Buildroot] [PATCH 2/4] package/arm-gnu-a-toolchain: new package sunil at amarulasolutions.com
2020-02-13 7:34 ` Sergey Matyukevich
2020-02-13 8:10 ` Jagan Teki
2020-02-13 9:20 ` Sergey Matyukevich
2020-02-13 9:43 ` Jagan Teki
2020-02-13 10:01 ` Sunil Kumar Mahesh
2020-02-14 4:19 ` Thomas Petazzoni [this message]
2020-02-14 4:17 ` Thomas Petazzoni
2020-02-13 5:52 ` [Buildroot] [PATCH 3/4] boot/arm-trusted-firmware: add support for rockchip rk3399 sunil at amarulasolutions.com
2020-02-14 8:25 ` Sergey Matyukevich
2020-02-14 9:35 ` Sunil Kumar Mahesh
2020-02-13 5:52 ` [Buildroot] [PATCH 4/4] configs/roc-rk3399-pc: new defconfig sunil at amarulasolutions.com
2020-02-13 8:22 ` Jagan Teki
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=20200214051925.1d3b6cc3@windsurf \
--to=thomas.petazzoni@bootlin.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.