diff options
| author | Ming Liu <ming.liu@toradex.com> | 2020-06-03 13:48:38 +0200 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-07-02 16:12:36 +0100 |
| commit | d7b8ae3faa9344f2ada22e0402066c2fff5958c6 (patch) | |
| tree | e63292854d572b3c6eb3bc86ee1a4cf496265736 /meta/recipes-core | |
| parent | abde5f4cab763c308ef3144055afebc6c87877d1 (diff) | |
| download | poky-d7b8ae3faa9344f2ada22e0402066c2fff5958c6.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: e4d5c99abab58aa813fe2da7c576ae69b9413304)
Signed-off-by: Ming Liu <ming.liu@toradex.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit fb7e8b6b88855f3f523b2176ea2c85a330bfe00b)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-core')
0 files changed, 0 insertions, 0 deletions