From: Patrick Delaunay <patrick.delaunay@st.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 0/9] env: ext4: corrections and add test for env in ext4
Date: Tue, 16 Jun 2020 09:40:39 +0200 [thread overview]
Message-ID: <20200616074048.7898-1-patrick.delaunay@st.com> (raw)
Hi,
V2 is only a rebase and adaptation of the serie [1].
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 [2]
"cmd: env: add option for quiet output on env info"
To be able to test invalid file (bad CRC), I also add the support of
the command "env erase" for EXT4 env location.
[1] http://patchwork.ozlabs.org/project/uboot/list/?series=158160
[2] http://patchwork.ozlabs.org/project/uboot/list/?series=183438
Regards
Patrick
Changes in v2:
- change cmd_tbl_t to struct cmd_tbl
- use CONFIG_IS_ENABLED to set .erase (same as .save)
Patrick Delaunay (9):
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: 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 | 52 +++++++++++++++
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 | 54 ++++++++++++---
test/py/tests/test_env.py | 103 +++++++++++++++++++++++++++++
9 files changed, 226 insertions(+), 10 deletions(-)
--
2.17.1
next reply other threads:[~2020-06-16 7:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 7:40 Patrick Delaunay [this message]
2020-06-16 7:40 ` [PATCH v2 1/9] env: add absolute path at CONFIG_ENV_EXT4_FILE Patrick Delaunay
2020-06-18 19:25 ` Tom Rini
2020-06-16 7:40 ` [PATCH v2 2/9] env: ext4: set gd->env_valid Patrick Delaunay
2020-06-18 19:25 ` Tom Rini
2020-06-16 7:40 ` [PATCH v2 3/9] env: correctly handle result in env_init Patrick Delaunay
2020-06-18 19:15 ` Tom Rini
2020-06-19 14:14 ` Patrick DELAUNAY
2020-06-19 18:05 ` Tom Rini
2020-06-23 13:13 ` Patrick DELAUNAY
2020-06-23 15:16 ` Tom Rini
2020-06-24 11:19 ` Patrick DELAUNAY
2020-06-24 18:07 ` Tom Rini
2020-06-16 7:40 ` [PATCH v2 4/9] sandbox: activate env in ext4 support Patrick Delaunay
2020-06-16 7:40 ` [PATCH v2 5/9] sandbox: support the change of env location Patrick Delaunay
2020-06-17 3:12 ` Simon Glass
2020-06-18 19:17 ` Tom Rini
2020-06-19 14:40 ` Patrick DELAUNAY
2020-06-19 18:07 ` Tom Rini
2020-06-16 7:40 ` [PATCH v2 6/9] test: environment in ext4 Patrick Delaunay
2020-06-22 18:57 ` Stephen Warren
2020-06-23 18:00 ` Patrick DELAUNAY
2020-06-16 7:40 ` [PATCH v2 7/9] env: ext4: introduce new function env_ext4_save_buffer Patrick Delaunay
2020-06-16 7:40 ` [PATCH v2 8/9] env: ext4: add support of command env erase Patrick Delaunay
2020-06-16 7:40 ` [PATCH v2 9/9] test: sandbox: add test for erase command Patrick Delaunay
2020-06-17 3:12 ` Simon Glass
2020-06-22 18:58 ` Stephen Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200616074048.7898-1-patrick.delaunay@st.com \
--to=patrick.delaunay@st.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox