From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] What if ATF can be part of U-Boot source, like SPL?
Date: Sun, 30 Jun 2019 13:15:38 +0200 [thread overview]
Message-ID: <20190630111538.E4E81241D29@gemini.denx.de> (raw)
In-Reply-To: <CAMty3ZDwHbkNr28m8Q1Q_F716S1tCU0Fhn3aurpWvkK58WyCXA@mail.gmail.com>
Dear Jagan,
In message <CAMty3ZDwHbkNr28m8Q1Q_F716S1tCU0Fhn3aurpWvkK58WyCXA@mail.gmail.com> you wrote:
> In terms of code maintenance and development feasibility it is always
> a better approach to have out-of-tree code or binary to be part of
> in-house source tree.
>
> This is what exactly it was done for SPL, if I'm not wrong. So can we
> do the same thing for ATF on ARM64 SoCs?
You are wrong. SPL has always been U-Boot internal code.
It may be true that some "external" early boot stages (line xloader)
have been replaced by SPL, but in no case such external code was
adaptes as is, and in the cases I am aware of this was original
U-Boot code anyway which hat just been forked off and maintained
out-of-tree.
But SPL is native U-Boot code only.
> We are using ATF (on Allwinner) to switch EL3 to EL2 for start loading
> U-Boot proper and minimal PSCI, PMIC initialization. So assuming the
> functionality of ATF (like here) is limited so the code it require can
> be limited too, so why can't this code to be part of U-Boot tree?
>
> This would ultimately avoid out-off-tree ATF builds with associated
> variable exporting during u-boot builds.
If U-Boot included a copy of the ATF code, it would have been forked
of the mainline ATF code at some point, so it is still out of tree.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Absolute: Independent, irresponsible. An absolute monarchy is one in
which the sovereign does as he pleases so long as he pleases the
assassins. Not many absolute monarchies are left, most of them having
been replaced by limited monarchies, where the soverign's power for
evil (and for good) is greatly curtailed, and by republics, which are
governed by chance. - Ambrose Bierce
next prev parent reply other threads:[~2019-06-30 11:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 15:02 [U-Boot] What if ATF can be part of U-Boot source, like SPL? Jagan Teki
2019-06-29 16:50 ` Mark Kettenis
2019-06-29 18:38 ` Marek Vasut
2019-06-29 18:49 ` André Przywara
2019-06-29 23:03 ` Marek Vasut
2019-06-30 1:38 ` André Przywara
2019-07-02 18:32 ` Marek Vasut
2019-09-04 2:17 ` Simon Glass
2019-09-04 17:32 ` Andre Przywara
2019-09-04 17:56 ` Marek Vasut
2019-09-05 0:54 ` André Przywara
2019-09-05 12:26 ` Marek Vasut
2019-09-05 23:14 ` André Przywara
2019-06-30 11:15 ` Wolfgang Denk [this message]
2019-06-30 13:57 ` Tom Rini
2019-06-30 14:03 ` Marek Vasut
2019-06-30 14:07 ` Michael Nazzareno Trimarchi
2019-06-30 14:17 ` Tom Rini
2019-06-30 14:20 ` Marek Vasut
2019-06-30 14:29 ` Tom Rini
2019-06-30 14:50 ` Marek Vasut
2019-09-04 2:51 ` Masahiro Yamada
2019-09-04 23:10 ` Tom Rini
[not found] <20190904134501.7980e45b@donnerap.cambridge.arm.com>
2019-09-05 1:17 ` Matteo Carlini
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=20190630111538.E4E81241D29@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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