]> code.ossystems Code Review - openembedded-core.git/commit
u-boot: introduce UBOOT_INITIAL_ENV
authorMing Liu <ming.liu@toradex.com>
Wed, 3 Jun 2020 11:48:38 +0000 (13:48 +0200)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 4 Jun 2020 12:21:01 +0000 (13:21 +0100)
commitfb7e8b6b88855f3f523b2176ea2c85a330bfe00b
tree355b7ff7fbefe1f9a2c9fbc68cf1722f57ec0c47
parent5ffefba5f1a7a37f4752e34be86f1dc2942192d0
u-boot: introduce UBOOT_INITIAL_ENV

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.liu@toradex.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-bsp/u-boot/u-boot.inc