public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] env: add ENV_IS_ANYWHERE
Date: Wed, 2 Aug 2017 20:48:13 -0400	[thread overview]
Message-ID: <20170803004813.GA29197@bill-the-cat> (raw)
In-Reply-To: <20170731124202.9500-1-robdclark@gmail.com>

On Mon, Jul 31, 2017 at 08:42:01AM -0400, Rob Clark wrote:

> Useful for devices which would otherwise have to use ENV_IS_NOWHERE.
> Tries to find and load uboot.env from any block device (which may be,
> for example, hot-pluggable sd-card, SATA or USB disk, so the exact
> location is not known at the time u-boot is compiled).
> 
> Signed-off-by: Rob Clark <robdclark@gmail.com>

I can see where this concept is useful.  What I would like to see is
updating the ENV_IS_IN_FAT / ENV_IS_IN_EXT4 / ENV_IS_ANYWHERE so that we
end up with:
- ENV_IS_IN_FILESYSTEM
  - Configured device, part, file.
  - Optional specify device, otherwise help for the option describes the
    logic behind how U-Boot will iterate until it finds something.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170802/b5d8b565/attachment.sig>

      parent reply	other threads:[~2017-08-03  0:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 12:42 [U-Boot] [PATCH] env: add ENV_IS_ANYWHERE Rob Clark
2017-07-31 12:42 ` [U-Boot] [PATCH] vsprintf.c: add wide string (%ls) support Rob Clark
2017-08-02  2:22   ` Heinrich Schuchardt
2017-08-02  9:38     ` Rob Clark
2017-08-02 17:05       ` Heinrich Schuchardt
2017-08-02 18:15         ` Rob Clark
2017-08-02 21:40           ` Heinrich Schuchardt
2017-08-02 22:25             ` Rob Clark
2017-08-03  0:48 ` Tom Rini [this message]

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=20170803004813.GA29197@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