Re: [U-Boot] [PATCH] env: common: load read-only variables after reset

2018-08-27 Thread Yaniv Levinsky
On 07/27/2018 06:34 PM, Yaniv Levinsky wrote: > U-Boot fails to load read-only variables from storage after a reset. It > happens because the environment hash table prevents creating read-only > variables unless the H_FORCE flag is passed. > > In the following example, the variable "test" is set t

Re: [U-Boot] [PATCH] env: common: load read-only variables after reset

2018-07-29 Thread Yaniv Levinsky
Hello Wolfgang, On 07/28/2018 03:56 PM, Wolfgang Denk wrote: > Dear Yaniv, > > In message <20180727153444.5602-1-yaniv.levin...@compulab.co.il> you wrote: >> U-Boot fails to load read-only variables from storage after a reset. It >> happens because the environment hash table prevents creating rea

Re: [U-Boot] [PATCH] env: common: load read-only variables after reset

2018-07-28 Thread Wolfgang Denk
Dear Yaniv, In message <20180727153444.5602-1-yaniv.levin...@compulab.co.il> you wrote: > U-Boot fails to load read-only variables from storage after a reset. It > happens because the environment hash table prevents creating read-only > variables unless the H_FORCE flag is passed. This is NOT a g

[U-Boot] [PATCH] env: common: load read-only variables after reset

2018-07-27 Thread Yaniv Levinsky
U-Boot fails to load read-only variables from storage after a reset. It happens because the environment hash table prevents creating read-only variables unless the H_FORCE flag is passed. In the following example, the variable "test" is set to read-only in the board header file (#define CONFIG_ENV