diff options
author | Quentin Schulz <quentin.schulz@theobroma-systems.com> | 2024-04-15 14:43:57 +0200 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2024-04-18 16:37:25 -0600 |
commit | 97b34f6ace539c9c16eb8565f8b58730848ba97a (patch) | |
tree | 46665c437ec30392b4e9d301db52f6ff555c6dce | |
parent | 84dda5ce3e3ba126f1bf83f87c84f27714b5fe4a (diff) | |
download | u-boot-WIP/18Apr2024.zip u-boot-WIP/18Apr2024.tar.gz u-boot-WIP/18Apr2024.tar.bz2 |
env: mmc: print MMC device being readWIP/18Apr2024
This prints the MMC device being read similar to how we print the MMC
device we write to when e.g. calling saveenv.
One of the side effects is that the boot log now shows from which MMC
device the env was loaded:
Loading Environment from MMC... Reading from MMC(1)... OK
This is useful to identify which MMC device the environment was loaded
from for boards where there are more than one (e.g. eMMC and SD card)
without adding some debug messages manually.
Sadly, there's no way to know which of the default or redundant
environment is being read from env_mmc_load before env_import_redund is
called so it is printing a bit later (and possibly after error/warning
messages).
Cc: Quentin Schulz <foss+uboot@0leil.net>
Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Dragan Simic <dsimic@manjaro.org>
-rw-r--r-- | env/mmc.c | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -436,6 +436,7 @@ static int env_mmc_load(void) ret = env_import_redund((char *)tmp_env1, read1_fail, (char *)tmp_env2, read2_fail, H_EXTERNAL); + printf("Reading from %sMMC(%d)... ", gd->env_valid == ENV_REDUND ? "redundant " : "", dev); fini: fini_mmc_for_env(mmc); @@ -475,6 +476,8 @@ static int env_mmc_load(void) goto fini; } + printf("Reading from MMC(%d)... ", dev); + ret = env_import(buf, 1, H_EXTERNAL); if (!ret) { ep = (env_t *)buf; |