From patchwork Wed Feb 12 18:44:51 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Patrick Delaunay X-Patchwork-Id: 236281 List-Id: U-Boot discussion From: patrick.delaunay at st.com (Patrick Delaunay) Date: Wed, 12 Feb 2020 19:44:51 +0100 Subject: [RESEND PATCH 00/10] env: ext4: add test for env in ext4 Message-ID: <20200212184501.5911-1-patrick.delaunay@st.com> Hi, [RESEND] with correct serie title (sorry) In this serie, I add sandbox test with CONFIG_ENV_IS_NOWHERE activated with other location: at least one CONFIG_ENV_IS_IN_... is defined and ENV_IS_IN_DEVICE is automatically defined. To test this feature, I activate and test ENV_IS_IN_EXT4 in sandbox; I add a new command "env_loc" to change this ENV location. This serie depends on previous env test introduced in: "cmd: env: add option for quiet output on env info" http://patchwork.ozlabs.org/project/uboot/list/?series=158105 To be able to test invalid file (bad CRC), I also add the support of the command "env erase" for EXT4 env location. Regards Patrick Patrick Delaunay (10): env: add absolute path at CONFIG_ENV_EXT4_FILE env: ext4: set gd->env_valid env: correctly handle result in env_init sandbox: activate env in ext4 support sandbox: support the change of env location test: environment in ext4 env: ext4: fix possible compilation issue env: ext4: introduce new function env_ext4_save_buffer env: ext4: add support of command env erase test: sandbox: add test for erase command board/sandbox/sandbox.c | 50 ++++++++++++++ configs/sandbox64_defconfig | 5 ++ configs/sandbox_defconfig | 5 ++ configs/sandbox_flattree_defconfig | 5 ++ configs/sandbox_spl_defconfig | 5 ++ env/Kconfig | 2 +- env/env.c | 5 +- env/ext4.c | 63 +++++++++++++++--- test/py/tests/test_env.py | 103 +++++++++++++++++++++++++++++ 9 files changed, 232 insertions(+), 11 deletions(-)