diff options
author | Ming Liu <ming.liu@toradex.com> | 2020-06-03 13:48:38 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-06-04 13:27:32 +0100 |
commit | e52d60d9d472460f2506bedb0ce109905dc590cf (patch) | |
tree | fa22429e8d4453955036af2103d926619c47adff /meta/lib | |
parent | 43dbbb87120d48c378e3b836d7d0788a91489655 (diff) | |
download | poky-e52d60d9d472460f2506bedb0ce109905dc590cf.tar.gz |
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.
(From OE-Core rev: fb7e8b6b88855f3f523b2176ea2c85a330bfe00b)
Signed-off-by: Ming Liu <ming.liu@toradex.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib')
0 files changed, 0 insertions, 0 deletions