Re: [U-Boot] [PATCH v2] fw_setenv: avoid writing environment when nothing has changed

2019-11-19 Thread Joe Hershberger
On Thu, Sep 27, 2018 at 3:45 PM Rasmus Villemoes wrote: > > In the case where one deletes an already-non-existing variable, or sets > a variable to the value it already has, there is no point in writing the > environment back, thus reducing wear on the underlying storage > device. > > In the case

Re: [U-Boot] [PATCH v2] fw_setenv: avoid writing environment when nothing has changed

2018-10-30 Thread Rasmus Villemoes
On 2018-09-27 22:45, Rasmus Villemoes wrote: > In the case where one deletes an already-non-existing variable, or sets > a variable to the value it already has, there is no point in writing the > environment back, thus reducing wear on the underlying storage > device. > > In the case of redundant

[U-Boot] [PATCH v2] fw_setenv: avoid writing environment when nothing has changed

2018-09-27 Thread Rasmus Villemoes
In the case where one deletes an already-non-existing variable, or sets a variable to the value it already has, there is no point in writing the environment back, thus reducing wear on the underlying storage device. In the case of redundant environments, if the two environments differ (e.g.