From: afaerber@suse.de (Andreas Färber)
To: linus-amlogic@lists.infradead.org
Subject: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
Date: Mon, 11 Jul 2016 06:41:35 +0200 [thread overview]
Message-ID: <5783237F.4090807@suse.de> (raw)
In-Reply-To: <CALeDE9OM__RZT7Re1+bHn0h41Hku9=k_yj_0hqiW8REjsYx0Uw@mail.gmail.com>
Am 11.07.2016 um 06:23 schrieb Peter Robinson:
> On Mon, Jul 11, 2016 at 4:57 AM, Andreas F?rber <afaerber@suse.de> wrote:
>> P.S. The upstream arm-trusted-firmware fip_create tool doesn't know
>> about --bl30 and --bl301 btw, anyone any insights?
>
> If you find details on the upstream ATF support I'd love a link for more details
https://github.com/ARM-software/arm-trusted-firmware/tree/master/tools/fip_create
I found a commit renaming BL3-0 to SCP_BL2, but no mention of BL3-0-1
beyond Hardkernel and this patchset.
https://github.com/ARM-software/arm-trusted-firmware/commit/f59821d51255f14e0ac00eef7bc98ef75c686876
$ make -C u-boot-hardkernel fip_create
$ ./u-boot-hardkernel/tools/fip_create/fip_create --dump fip.bin
Firmware Image Package ToC:
---------------------------
- SCP Firmware BL3-0: offset=0x4000, size=0x9E88
- SCP Firmware BL3-0-1: offset=0x10000, size=0x1758
- EL3 Runtime Firmware BL3-1: offset=0x14000, size=0x110D0
- Non-Trusted Firmware BL3-3: offset=0x28000, size=0x36AF6
---------------------------
$ make -C arm-trusted-firmware fiptool
$ ./arm-trusted-firmware/tools/fip_create/fip_create --dump fip.bin
Firmware Image Package ToC:
---------------------------
- SCP Firmware SCP_BL2: offset=0xD8, size=0x9E88
- Unknown entry: offset=0x9F60, size=0x1758
- EL3 Runtime Firmware BL31: offset=0xB6B8, size=0x110D0
- Non-Trusted Firmware BL33: offset=0x1C788, size=0x36AF6
---------------------------
Note that the offsets for BL30[1] are shown differently.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2016-07-11 4:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 6:30 [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support Beniamino Galvani
2016-05-08 6:30 ` [PATCH v7 1/4] arm: implement generic PSCI reset call for armv8 Beniamino Galvani
2016-05-19 3:59 ` Simon Glass
2016-05-30 17:57 ` [U-Boot,v7,1/4] " Tom Rini
2016-05-30 17:57 ` Tom Rini
2016-05-08 6:30 ` [PATCH v7 2/4] net: designware: fix descriptor layout and warnings on 64-bit archs Beniamino Galvani
2016-05-19 3:59 ` Simon Glass
2016-05-30 17:57 ` [U-Boot, v7, " Tom Rini
2016-05-08 6:30 ` [PATCH v7 3/4] arm: add initial support for Amlogic Meson and ODROID-C2 Beniamino Galvani
2016-05-19 3:59 ` Simon Glass
2016-05-20 14:44 ` Carlo Caione
2016-05-30 17:57 ` [U-Boot, v7, " Tom Rini
2016-05-08 6:30 ` [PATCH v7 4/4] arm: meson: implement calls to secure monitor Beniamino Galvani
2016-05-30 17:57 ` [U-Boot,v7,4/4] " Tom Rini
2016-05-29 16:38 ` [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support Carlo Caione
2016-05-29 17:09 ` Tom Rini
2016-07-11 3:57 ` [U-Boot] " Andreas Färber
2016-07-11 4:23 ` Peter Robinson
2016-07-11 4:41 ` Andreas Färber [this message]
2016-07-11 19:48 ` Beniamino Galvani
2016-07-11 20:15 ` Andreas Färber
2016-07-11 20:36 ` Carlo Caione
2016-07-11 21:38 ` Andreas Färber
2016-07-11 22:52 ` Carlo Caione
2016-07-11 22:54 ` Andreas Färber
2016-07-11 23:04 ` Carlo Caione
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=5783237F.4090807@suse.de \
--to=afaerber@suse.de \
--cc=linus-amlogic@lists.infradead.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 NNTP newsgroup(s).