From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v2 5/9] sandbox: support the change of env location
Date: Fri, 19 Jun 2020 14:07:51 -0400 [thread overview]
Message-ID: <20200619180751.GQ27801@bill-the-cat> (raw)
In-Reply-To: <817efefe407341aa98d6a80f037a1610@SFHDAG6NODE3.st.com>
On Fri, Jun 19, 2020 at 02:40:06PM +0000, Patrick DELAUNAY wrote:
> Hi,
>
> > From: Tom Rini <trini@konsulko.com>
> > Sent: jeudi 18 juin 2020 21:17
> >
> > On Tue, Jun 16, 2020 at 09:40:44AM +0200, Patrick Delaunay wrote:
> >
> > > Add support of environment location with a new sandbox command
> > > 'env_loc'.
> > >
> > > When the user change the environment location with the command
> > > 'env_loc <location>' the env is reinitialized and saved; the
> > > GD_FLG_ENV_DEFAULT flag is also updated.
> > >
> > > When the user set the same env location, the environment is re-loaded.
> > >
> > > Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
> > > ---
> > >
> > > Changes in v2:
> > > - change cmd_tbl_t to struct cmd_tbl
> > >
> > > board/sandbox/sandbox.c | 42
> > > ++++++++++++++++++++++++++++++++++++++++-
> > > 1 file changed, 41 insertions(+), 1 deletion(-)
> >
> > This is for testing, which is why it's on sandbox? But I think we should have this
> > be a generic opt-in feature as changing where environment is saved at run time
> > has use cases when we have multiple available. Thanks!
>
> Yes in my mind it was only for testing on sandbox....
>
> But I agree, I can a add a opt-in generic command to select and load ENV on one target.
>
> Someting as "env load [<target>] " which loads with the request backend and update gd->env_load_prio
>
> With <target> = name of the name define in backend with ENV_NAME macro
> And using the default location gd->env_load_prio when absent.
>
> Or split in 2 new commands
>
> - env select <target>
> - env load
>
> Perhaps this last proposal with 2 command is more flexible....
> to be combined with other command (env save / env erase)
>
> if this proposal is OK, I will work on it.....
Sounds good to me, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200619/b992f1a8/attachment.sig>
next prev parent reply other threads:[~2020-06-19 18:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 7:40 [PATCH v2 0/9] env: ext4: corrections and add test for env in ext4 Patrick Delaunay
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 [this message]
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=20200619180751.GQ27801@bill-the-cat \
--to=trini@konsulko.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