From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 02/11] support/scripts: Add sunxi64-post-build.sh
Date: Sun, 22 Oct 2017 14:29:19 +0200 [thread overview]
Message-ID: <20171022142919.6dc03525@windsurf> (raw)
In-Reply-To: <4cb45577-1f4a-ce9c-7204-74934272b789@arm.com>
Hello,
On Sun, 22 Oct 2017 12:05:52 +0100, Andr? Przywara wrote:
> > This wasn't only the case with sunxi it's been the U-Boot FIT
> > behaviour..even rockchip do follow same build process.
> >
> > Ideally FIT need input files to produce blob like dtb.
> >
> > Added Andre he will give some more insight.
>
> So yes, ATF supports *multiple* ways of integration:
> - On the Juno it has the capability of loading images - from NOR flash,
> so not a big deal. This means the BL1 and BL2 stages read the BL31
> (containing the PSCI runtime) and BL33 (U-Boot or EDK2), also this uses
> the ATF defined FIP image format.
> - For other platforms (like rockchip or sunxi) we usually load from MMC
> or SPI flash. So using the traditional ATF approach would mean to have
> MMC and SPI drivers in the early ATF stages, also do the DRAM
> initialization there. Since ATF is BSD licensed, it's more involved than
> just copying some code from U-Boot.
> So the pragmatic approach - which ATF actually embraces - is to just use
> a subset of the whole ATF (BL31) and do the rest via some platform
> specific firmware: which is U-Boot's SPL in our case, since it already
> has support for this hardware. Other platform (most ARM64 servers) tend
> to have their proprietary early-init firmware there.
Thanks for summarizing the context.
> So I virtually know nothing about buildroot, but it might not be a good
> idea to shoehorn the second approach into the Juno ATF build scheme.
> As I believe that in fact more platforms use the second approach, it
> might be worthwhile to introduce some extra code in buildroot to support
> that specifically instead of working around the Juno ATF way.
> Maybe it can be modelled as some U-Boot FIT build process with an
> additional requirement, similar to a binary blob?
And this is exactly what I was suggesting Jagan to do: extend Buildroot
so that it covers the U-Boot-bundles-ATF scenario (sunxi/rockchip,
etc.) in addition to the already supported ATF-bundles-U-Boot scenario
(Juno).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-22 12:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 9:45 [Buildroot] [PATCH v3 00/11] board: Add Allwinner A64/H5 boards Jagan Teki
2017-10-19 9:45 ` [Buildroot] [PATCH v3 01/11] board: Add Bananapi M1 support Jagan Teki
2017-10-19 10:38 ` Baruch Siach
2017-10-19 10:56 ` Jagan Teki
2017-10-21 20:37 ` Thomas Petazzoni
2017-10-19 9:45 ` [Buildroot] [PATCH v3 02/11] support/scripts: Add sunxi64-post-build.sh Jagan Teki
2017-10-21 21:06 ` Thomas Petazzoni
2017-10-22 10:15 ` Jagan Teki
[not found] ` <4cb45577-1f4a-ce9c-7204-74934272b789@arm.com>
2017-10-22 12:29 ` Thomas Petazzoni [this message]
2017-10-26 11:20 ` Jagan Teki
2017-10-26 18:13 ` Jagan Teki
[not found] ` <e73be7ab-6435-5d11-41b5-37f3bf4053ee@arm.com>
2017-10-27 11:46 ` Jagan Teki
2017-10-19 9:45 ` [Buildroot] [PATCH v3 03/11] board: Add Bananapi M64 support Jagan Teki
2017-10-19 9:45 ` [Buildroot] [PATCH v3 04/11] board: Add Pine64 support Jagan Teki
2017-10-19 9:45 ` [Buildroot] [PATCH v3 05/11] board: Add SoPine support Jagan Teki
2017-10-19 9:45 ` [Buildroot] [PATCH v3 06/11] board: Add FriendlyARM Nanopi A64 support Jagan Teki
2017-10-19 9:45 ` [Buildroot] [PATCH v3 07/11] board: Add FriendlyARM Nanopi NEO2 support Jagan Teki
2017-10-19 9:45 ` [Buildroot] [PATCH v3 08/11] board: Add Olimex A64-OLinuXino support Jagan Teki
2017-10-19 9:45 ` [Buildroot] [PATCH v3 09/11] board: Add Orangepi Win/Win Plus support Jagan Teki
2017-10-19 9:45 ` [Buildroot] [PATCH v3 10/11] board: Add Orangepi Prime support Jagan Teki
2017-10-19 9:45 ` [Buildroot] [PATCH v3 11/11] board: Add Orangepi Zero Plus2 support 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=20171022142919.6dc03525@windsurf \
--to=thomas.petazzoni@free-electrons.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