From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v2, 2/2] Kconfig: Add u-boot.itb BUILD_TARGET for Rockchip
Date: Fri, 1 Feb 2019 22:35:43 -0500 [thread overview]
Message-ID: <20190202033543.GO30838@bill-the-cat> (raw)
In-Reply-To: <20190118072341.20227-1-jagan@amarulasolutions.com>
On Fri, Jan 18, 2019 at 12:53:41PM +0530, Jagan Teki wrote:
> Add u-boot.itb BUILD_TARGET for Rockchip platform when SPL_LOAD_FIT
> is being used. This can get rid of building itb explicitly with
> 'make u-boot.itb' all required images will now build just by make.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
So, we have a problem. Two actually, but the first is easily fixed.
The first is that in travis, we need python-pyelftools in order for the
python script to run. The second and harder problem is seen here:
https://travis-ci.org/trini/u-boot/jobs/487680727
where we need to adapt the script to return a success error code and
scream at the end user that the resulting binary is not valid. We have
this on all the other aarch64 platforms that have a default build target
that requires BL31, etc, and need it on rockchip with this patch.
I'd also really appreciate if someone could look at the N different
wrappers and see if we can't get something more common as it looks like
that for example between i.MX8 and Rockchip we have a lot of common
ground (make a FIT) and then just a binary modification at the end for
rockchip?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190201/3565ce7a/attachment.sig>
next prev parent reply other threads:[~2019-02-02 3:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 7:23 [U-Boot] [PATCH v2 2/2] Kconfig: Add u-boot.itb BUILD_TARGET for Rockchip Jagan Teki
2019-02-02 3:35 ` Tom Rini [this message]
2019-04-18 6:10 ` [U-Boot] [U-Boot, v2, " 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=20190202033543.GO30838@bill-the-cat \
--to=trini@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.