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:17:50 +0100 [thread overview]
Message-ID: <20200214051750.5877034f@windsurf> (raw)
In-Reply-To: <20200213092005.o5h7wioo2kokn2gr@bars>
On Thu, 13 Feb 2020 12:20:05 +0300
Sergey Matyukevich <geomatsi@gmail.com> wrote:
> > > Could you please clarify why a separate toolchain is required to build
> > > ATF for this platform ? Is there any specific requirements other than
> > > this particular build error ?
> >
> > Rockchip rk3399 has cortex-m0 and these changes are build during ATF.
> > and then environment should have arm32 cross toolchain to make it
> > build successfully.
> >
> > I think, Sunil need to write something more on this requirement on
> > commit message.
>
> Well, I mean that other ATF firmwares can be built with standard buildroot
> toolchain. I guess this is the case for Rockchip ATF as well. You just need
> to specify available toolchain using environment variable or something.
> In the worst case, some patch modifing Makefiles in Rockchip ATF
> source tree is needed.
No, this is not correct. Depending on the platform, ATF may include
code that runs on ARM32 co-processors, and ARM32 code cannot be built
with an ARM64 toolchain.
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:17 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
2020-02-14 4:17 ` Thomas Petazzoni [this message]
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=20200214051750.5877034f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox