In the old u-boot-fw-utils 2016.x the function 'fw_env_close' wrote the environment to the media. That is no longer the case, now that function only frees the memory used, and 'fw_env_flush' is used to write the environment. This was causing that userspace application using this library were not able to write changes to the environment. https://jira.digi.com/browse/DEL-5644 Signed-off-by: Jose Diaz de Grenu <Jose.DiazdeGrenu@digi.com> |
||
|---|---|---|
| .. | ||
| ccimx6 | ||
| ccimx6ul | ||
| 0001-tools-env-implement-support-for-environment-encrypti.patch | ||
| 0002-Implement-U-Boot-environment-access-functions.patch | ||
| 0003-fw_env-add-support-to-unlock-emmc-boot-partition.patch | ||
| 0004-tools-env-add-support-to-set-dynamic-location-of-env.patch | ||