On Wed, Apr 03, 2019 at 01:30:47PM +0000, Molloy, Philip wrote: > fw_setenv and fw_printenv currently print a warning and use a default > environment compiled into the binary when an invalid CRC is found. This > modifies the default behavior to print an error and exit. This is > especially important when calling the tools from a script since the > script depends on the exit code of the tool to know something went > wrong. > > If the default environment is desired it should be read explicitly by > the caller. A better model is to store a default environment as a > separate binary or text file rather than storing it in the executable. > > Signed-off-by: Philip Molloy <philip-mol...@idexx.com>
Conceptually, yes, this is correct. However, the behavior in question has been deployed for so long that I don't feel that we can change it at this point, so I'm going to NAK this. Sorry. -- Tom
signature.asc
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
