Hello,
in message <[EMAIL PROTECTED]> you wrote:
>
> I just had the problem of fw_{print,save}env not being able to access
> the environment because I was using the default (builtin) environment
> after flashing U-Boot.
> I wonder if I am the only one having this problem, or is it common
> practice to flash the environment together with U-Boot during production?
Quite a number of boards use an embedded environment which gets
auto-installed when programming the U-Boot image. And a significant
percentage of boards I know use some installation tool that will set
up things like serial number, MAC addresses etc. one way or another,
andin many cases this includes running "saveenv".
> I just made this small patch to auto-save the environment if it is
> not found in flash but am wondering if
> - I missed something and such a possibility does already exist?
No, and I strongly discourage it. It just makes detection of certain
types of problems / hardware errors etc. more difficult or even
impossible.
> - something similar might be worth considering as a new regular feature?
I think I would oppose such a change because I consider it really
dangerous.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED]
Genitiv ins Wasser, weil's Dativ ist!
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
U-Boot-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/u-boot-users
