On Thu, Jun 18, 2020 at 5:19 PM Andreas Müller <schnitzelt...@gmail.com> wrote:
>
> From: Ming Liu <ming....@toradex.com>
>
> It defaults to ${PN}-initial-env, no functional changes with current
> implementation, but this allows it to be changed in individual u-boot
> recipes.
>
> If UBOOT_INITIAL_ENV is empty, then no initial env would be compiled/
> installed/deployed, set ALLOW_EMPTY_${PN}-env = "1".
>
> The major purpose for introducing this, is that the users might have
> some scripts on targets like:
> ```
> /sbin/fw_setenv -f /etc/u-boot-initial-env
> ```
>
> and it should be able to run against a identical path generated by
> different u-boot recipes.
>
> Signed-off-by: Ming Liu <ming....@toradex.com>
> Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org>
> (cherry picked from commit fb7e8b6b88855f3f523b2176ea2c85a330bfe00b)
I'd like to do a little advertisement for this. This patch:* is mandatory to build older versions of u-boot. They do not support make target u-boot-initial-env and are buildable only by setting UBOOT_INITIAL_ENV="" introduced by this patch. * does not introduce functional change when keeping UBOOT_INITIAL_ENV untouched. Regards Andreas
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#139902): https://lists.openembedded.org/g/openembedded-core/message/139902 Mute This Topic: https://lists.openembedded.org/mt/74960680/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
