On Tue, May 21, 2019 at 10:24:10AM +0100, Alex Kiernan wrote:
On Tue, May 21, 2019 at 10:14 AM Eugeniu Rosca erosca@de.adit-jv.com wrote:
[..]
That's a truly constructive suggestion. Nevertheless, I believe this would not work in case of CONFIG_ENV_IS_NOWHERE=y, which is how U-Boot is built and used by the developers in our organization.
That's how we build/run too, but with with hackery like this in a boot script to pick pieces out of the legacy world:
mmc dev ${mmcdev} mmc read ${loadaddr} 1300 100 env import -c ${loadaddr} 20000 ethaddr
FWIW, we have a cascaded load of boot scripts combined with `env import -t` and/or `source`, which allows to control the boot media by changing one line in a text file. This might be super ugly in terms of vanilla standards, but it works in the development environment and that's what matters the most.