From: Maxime Ripard <maxime.ripard@bootlin.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] u-boot: remove driver lookup loop from env_save()
Date: Wed, 11 Jul 2018 15:47:35 +0200 [thread overview]
Message-ID: <20180711134735.vhhc7quuzcp42bo7@flea> (raw)
In-Reply-To: <20180711104950.7979324051B@gemini.denx.de>
On Wed, Jul 11, 2018 at 12:49:50PM +0200, Wolfgang Denk wrote:
> Dear Maxime,
>
> In message <20180711094838.zyczks6iksp772ir@flea> you wrote:
> >
> > I don't really see a use-case for overriding wherever the environment
> > at the user-level actually. At the board level, for redundancy or
> > transition, yes, definitely, but we can already do that.
>
> If the feature is available, use cases will spring into mind.
>
> Assume you have a eMMC based system which can also boot from other
> storage (say, SDCard), and you want to write the current content of
> the eMMC environment to the alternative boot device.
>
> Yes, there are usually alternative approaches to perform similar
> actions, but an easy way to save lsewhere might be handy, especially
> if it comes at low cost.
Right, but that would bring a much more significant rework as to how
the environments are handled than just the changes that are being
discussed here. At the moment, the environment can only be stored on
one device for each "types" (one raw MMC, one MTD partition, etc). The
redundancy allows you to duplicate it, but you won't be able to store
on just one instance of your choosing at the moment.
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180711/67b7e1f8/attachment.sig>
next prev parent reply other threads:[~2018-07-11 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 12:57 [U-Boot] [RFC PATCH] u-boot: remove driver lookup loop from env_save() Nicholas Faustini
2018-07-10 20:49 ` Simon Glass
2018-07-11 4:57 ` Simon Goldschmidt
2018-07-11 5:09 ` Simon Goldschmidt
2018-07-11 8:33 ` Nicholas
2018-07-11 9:48 ` Maxime Ripard
2018-07-11 10:01 ` Simon Goldschmidt
2018-07-11 10:44 ` Nicholas
2018-07-11 13:50 ` Maxime Ripard
2018-07-12 7:02 ` Simon Goldschmidt
2018-07-12 7:20 ` Maxime Ripard
2018-07-17 4:48 ` Simon Goldschmidt
2018-07-11 10:49 ` Wolfgang Denk
2018-07-11 13:47 ` Maxime Ripard [this message]
2018-07-11 13:54 ` Wolfgang Denk
2018-07-11 7:37 ` Lukasz Majewski
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=20180711134735.vhhc7quuzcp42bo7@flea \
--to=maxime.ripard@bootlin.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