Re: [U-Boot] [PATCH] fw_env.c: use default env values if config file cannot be opened

2012-02-12 Thread Wolfgang Denk
Dear Frans, In message you wrote: > > > As you mentioned in another reply the common practice nowadays seems to be > to use a conf file. > This has the disadvantage that the conf file can get lost or misplaced. True. And this is an error situation, for wich a proper error message should be is

Re: [U-Boot] [PATCH] fw_env.c: use default env values if config file cannot be opened

2012-01-05 Thread Frans Meulenbroeks
2012/1/5 Wolfgang Denk > Dear Frans Meulenbroeks, > > In message <1325098913-29909-1-git-send-email-fransmeulenbro...@gmail.com> > you wrote: > > If the config file cannot be opened currently one gets an error > > even though the build in names/sizes are probably ok. > > By setting the default va

Re: [U-Boot] [PATCH] fw_env.c: use default env values if config file cannot be opened

2012-01-05 Thread Wolfgang Denk
Dear Frans Meulenbroeks, In message <1325098913-29909-1-git-send-email-fransmeulenbro...@gmail.com> you wrote: > If the config file cannot be opened currently one gets an error > even though the build in names/sizes are probably ok. > By setting the default values first and only exit if there > i

[U-Boot] [PATCH] fw_env.c: use default env values if config file cannot be opened

2011-12-28 Thread Frans Meulenbroeks
If the config file cannot be opened currently one gets an error even though the build in names/sizes are probably ok. By setting the default values first and only exit if there is a read error and not when the config file can be opened the program will try the default settings. In order to detect