On Tue, Jun 18, 2019 at 12:40 PM Kever Yang <kever.yang@xxxxxxxxxxxxxx> wrote: > > Hi Jagan, > > > On 06/13/2019 02:53 PM, Jagan Teki wrote: > > Hi Kever, > > > > On Wed, May 8, 2019 at 12:23 AM Jagan Teki <jagan@xxxxxxxxxxxxxxxxxxxx> wrote: > >> RK3399 TPL changes are merged recently which I was thinking > >> of waiting for next MW. so this series skip binman changes > >> from previous version[1] and have only BUILD_TARGET changes. > >> > >> BINMAN changes would need another rework, where we need to consider > >> the TPL image as well and that would send separately. > >> > >> CHanges for v3: > >> - skip binman changes > >> - rebase on u-boot-rockchip/master > >> > >> [1] https://patchwork.ozlabs.org/cover/1092198/ > >> > >> 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 > > I think you hold for this with puma changes? any further comments > > please let me know. > > > > Yes, one reason is not get response from puma board. > And I think this does not break the board support but maybe > break the build process if not all the environment has export as expected? It can't break the build, for not exporting cases the script will create dummy bl31 elf and the bl31 variable assign it and finally trigger warning. fyi, the else statement on this patch [1] does what I mentioned. [1] https://patchwork.ozlabs.org/patch/1096505/ _______________________________________________ Linux-rockchip mailing list Linux-rockchip@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/linux-rockchip
