From: Ivan Mikhaylov <i.mikhaylov at yadro.com>
fw_setenv usage always locks u-boot-env mtd device without questions.
Locking of flash can be disruptive and may affect not only u-boot-env
region due to different problems with chips and lock callbacks on kernel
side. I'm not sure if my fix is right, but also I thought about possible option
in fw_env config about locking/unlocking or even option into
fw_setenv/printenv. Any ideas?
Ivan Mikhaylov (1):
fw_setenv: lock the flash only if it's already locked before
tools/env/fw_env.c | 24 +++++++++++++++++++++-----
1 file changed, 19 insertions(+), 5 deletions(-)
From: Ivan Mikhaylov <i.mikhaylov at yadro.com> fw_setenv usage always locks u-boot-env mtd device without questions. Locking of flash can be disruptive and may affect not only u-boot-env region due to different problems with chips and lock callbacks on kernel side. I'm not sure if my fix is right, but also I thought about possible option in fw_env config about locking/unlocking or even option into fw_setenv/printenv. Any ideas? Ivan Mikhaylov (1): fw_setenv: lock the flash only if it's already locked before tools/env/fw_env.c | 24 +++++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-)