From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] env_mmc: support overriding mmc dev from board code
Date: Wed, 20 Jan 2016 09:57:59 -0700 [thread overview]
Message-ID: <569FBC97.3060904@wwwdotorg.org> (raw)
In-Reply-To: <1453301017-6705-1-git-send-email-clemens.gruber@pqgruber.com>
On 01/20/2016 07:43 AM, Clemens Gruber wrote:
> This enables boards to choose where to/from the environment should be
> saved/loaded. They can then for example support using the same device
> (dynamically) from which the bootloader was launched to load and save
> env data and do not have to define CONFIG_SYS_MMC_ENV_DEV statically.
>
> In my use case, the environment needs to be on the same device I
> booted from. It can be the eMMC or an optional SD card.
> I therefore would override mmc_get_env_dev in the board code, read the
> CPU registers to determine where we booted from and return the
> corresponding device index.
Reviewed-by: Stephen Warren <swarren@nvidia.com>
I was going to ask: What about the HW partition number and offset, but
it appears that there is already a method to override those at run-time:-)
next prev parent reply other threads:[~2016-01-20 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 14:43 [U-Boot] [PATCH] env_mmc: support overriding mmc dev from board code Clemens Gruber
2016-01-20 16:57 ` Stephen Warren [this message]
2016-01-21 19:10 ` Tom Rini
2016-01-25 21:28 ` [U-Boot] " Tom Rini
2016-01-26 1:42 ` Peng Fan
2016-01-26 2:13 ` Tom Rini
2016-01-26 2:53 ` Peng Fan
2016-01-26 9:52 ` Clemens Gruber
2016-01-26 15:00 ` Tom Rini
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=569FBC97.3060904@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.