[PATCH] Revert "env: Load env when ENV_IS_NOWHERE is only location selected"
Felix.Vietmeyer at jila.colorado.edu
Felix.Vietmeyer at jila.colorado.edu
Wed Apr 13 02:49:29 CEST 2022
I am not exactly sure to be honest. We were running with this patched
version for a while and it worked from what I remember.
But we have since updated u-boot and the Kernel and the latest version
does not depend on this patch.
Nevertheless, I can try to recreate the problem and see if I can figure it
out now. I feel like I might pick up on a few more things now that went
unnoticed by me when I created the patch.
> On 4/10/22 13:54, Felix.Vietmeyer at jila.colorado.edu wrote:
>>>From your description it seems like the board I was working on must have
>> had an environment on NOR or eMMC which could be loaded but did not
>> allow
>> the board to come up.
>> Then, the patch forces u-boot to use the default environment despite an
>> existing env on NOR or eMMC.
>
> I suspect the board must have some other problem with the environment.
> I just cannot tell what it is. This is using some downstream U-Boot
> fork, right ? Can you reproduce the problem in mainline too ? How ?
>
More information about the U-Boot
mailing list