From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 0/6] rockchip: rk3399: Make u-boot.itb as BUILD_TARGET
Date: Thu, 20 Jun 2019 15:37:34 +0530 [thread overview]
Message-ID: <20190620100740.6560-1-jagan@amarulasolutions.com> (raw)
This is v4 set for supporting u-boot.itb build target
image for rk3399. here is the previous version changes[1]
Changes for v4:
- rebase on master
- support u-boot.itb build even if bl31.elf available
in PWD like what is doing right now. this would keep
the backward compatible.
- update board README changes
Changes for v3:
- skip binman changes
- rebase on u-boot-rockchip/master
Note:
While creating dummy bl31.elf (neither it available in PWD nor it
as part of BL31 env), the build system is creating u-boot.its without
firmware entry which indeed expected. but the resulting u-boot.itb
seems booting on rk3399, which I'm not sure - any input would help
on this regard.
Travis-CI:
https://travis-ci.org/openedev/u-boot-amarula/builds/548123247
[1] https://patchwork.ozlabs.org/cover/1096499/
Any inputs?
Jagan.
Jagan Teki (6):
Makefile: clean image.map
Makefile: clean bl31_*.bin
travis.yml: Add pyelftools install entry
rockchip: rk3399: Get bl31.elf via BL31
board: puma: Get bl31.bin via BL31 and rk3399m0.bin via PMUM0
Kconfig: Add u-boot.itb BUILD_TARGET for Rockchip
.travis.yml | 1 +
Kconfig | 2 +-
Makefile | 3 +-
arch/arm/mach-rockchip/make_fit_atf.py | 20 +++-
board/theobroma-systems/puma_rk3399/README | 2 +-
.../puma_rk3399/fit_spl_atf.its | 58 ------------
.../puma_rk3399/fit_spl_atf.sh | 94 +++++++++++++++++++
board/vamrs/rock960_rk3399/README | 1 -
configs/puma-rk3399_defconfig | 2 +-
doc/README.rockchip | 14 ++-
10 files changed, 124 insertions(+), 73 deletions(-)
delete mode 100644 board/theobroma-systems/puma_rk3399/fit_spl_atf.its
create mode 100755 board/theobroma-systems/puma_rk3399/fit_spl_atf.sh
--
2.18.0.321.gffc6fa0e3
next reply other threads:[~2019-06-20 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 10:07 Jagan Teki [this message]
2019-06-20 10:07 ` [U-Boot] [PATCH v4 1/6] Makefile: clean image.map Jagan Teki
2019-06-20 10:07 ` [U-Boot] [PATCH v4 2/6] Makefile: clean bl31_*.bin Jagan Teki
2019-06-20 10:07 ` [U-Boot] [PATCH v4 3/6] travis.yml: Add pyelftools install entry Jagan Teki
2019-06-20 10:07 ` [U-Boot] [PATCH v4 4/6] rockchip: rk3399: Get bl31.elf via BL31 Jagan Teki
2019-06-21 9:38 ` Kever Yang
2019-06-20 10:07 ` [U-Boot] [PATCH v4 5/6] board: puma: Get bl31.bin via BL31 and rk3399m0.bin via PMUM0 Jagan Teki
2019-06-21 9:39 ` Kever Yang
2019-06-20 10:07 ` [U-Boot] [PATCH v4 6/6] Kconfig: Add u-boot.itb BUILD_TARGET for Rockchip 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=20190620100740.6560-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--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