| Message ID | 20190507185215.15441-1-jagan@amarulasolutions.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | rockchip: rk3399: Make u-boot.itb as BUILD_TARGET | expand |
Hi Kever, On Wed, May 8, 2019 at 12:23 AM Jagan Teki <jagan@amarulasolutions.com> 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.
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@amarulasolutions.com> 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? Thanks, - Kever
On Tue, Jun 18, 2019 at 12:40 PM Kever Yang <kever.yang@rock-chips.com> 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@amarulasolutions.com> 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/
On 06/18/2019 03:16 PM, Jagan Teki wrote: > On Tue, Jun 18, 2019 at 12:40 PM Kever Yang <kever.yang@rock-chips.com> 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@amarulasolutions.com> 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 Could you create dummy bl31.elf after check if there is one already there, which is what we used to do instead of use BL31 env, and then this won't break anything and we can migrate to use BL31 smoothly. Thanks, - Kever > 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@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-rockchip >