From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Jagan Teki <jagan@amarulasolutions.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Cc: linux-rockchip@lists.infradead.org,
U-Boot-Denx <u-boot@lists.denx.de>,
Akash Gajjar <akash@openedev.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
linux-amarula <linux-amarula@amarulasolutions.com>
Subject: Re: [PATCH 0/5] rk3399: make u-boot-rockchip-with-spl.bin
Date: Fri, 26 Apr 2019 19:55:40 +0200 [thread overview]
Message-ID: <90241d1e39fde80f674008878f136e121b5bc6a4.camel@bootlin.com> (raw)
In-Reply-To: <CAMty3ZDqzeRsWvNnPMeAKuhwqfuJm8-Um9fcb+JE=jN3DV7KVw@mail.gmail.com>
Le vendredi 26 avril 2019 à 23:22 +0530, Jagan Teki a écrit :
> Hi Tom and Simon,
>
> On Fri, Apr 26, 2019 at 7:04 PM Jagan Teki <jagan@amarulasolutions.com> wrote:
> > This series will create single bootable image 'u-boot-rockchip-with-spl.bin'
> > for rk3399 platform with single make command instead of building u-boot
> > separately for u-boot.itb and burn them separately for SPL and U-Boot proper.
> >
> > This series has dependecy with[1]
> >
> > travis-ci issue:
> > - need to include 'python-pyelftools' package, tried but can't succeed
> > - right now build failed if BL31 is not exported, but this would manage to
> > create dummy arm64 elf but any help on this would appreciate.
>
> Any inputs on this?
I think we have the same issue regarding BL31 for ARM64 sunxi boards
don't we?
It would be great to have a solution to this, and even better if it
could scale to most ARM64 platforms too!
Cheers,
Paul
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
next prev parent reply other threads:[~2019-04-26 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 13:34 [PATCH 0/5] rk3399: make u-boot-rockchip-with-spl.bin Jagan Teki
[not found] ` <20190426133430.17802-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-04-26 13:34 ` [PATCH 1/5] arm64: rockchip: dts: rk3399: Create -u-boot.dtsi files Jagan Teki
[not found] ` <20190426133430.17802-2-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-04-26 18:00 ` Paul Kocialkowski
[not found] ` <ed9636781f6a0f2f648506a46bff6a656b93ceb2.camel-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
2019-04-26 18:09 ` Jagan Teki
2019-04-26 13:34 ` [PATCH 2/5] rockchip: rk3399: Get bl31.elf via BL31 env Jagan Teki
2019-04-26 13:34 ` [PATCH 3/5] Kconfig: Add u-boot.itb BUILD_TARGET for Rockchip Jagan Teki
2019-04-26 13:34 ` [PATCH 4/5] Makefile.spl: Create u-boot-spl-rockchip.bin for rk3399 Jagan Teki
2019-04-26 13:34 ` [PATCH 5/5] rockchip: rk3399: Create single image using BINMAN Jagan Teki
2019-04-26 17:52 ` [PATCH 0/5] rk3399: make u-boot-rockchip-with-spl.bin Jagan Teki
2019-04-26 17:55 ` Paul Kocialkowski [this message]
2019-04-26 17:59 ` Tom Rini
2019-04-26 18:03 ` 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=90241d1e39fde80f674008878f136e121b5bc6a4.camel@bootlin.com \
--to=paul.kocialkowski@bootlin.com \
--cc=akash@openedev.com \
--cc=jagan@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=sjg@chromium.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox