From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] common: env_mmc: Make mmc->part_num in sync after a partition switch
Date: Tue, 04 Jun 2013 12:28:41 -0600 [thread overview]
Message-ID: <51AE31D9.3040502@wwwdotorg.org> (raw)
In-Reply-To: <1370370223-7087-1-git-send-email-fabio.estevam@freescale.com>
On 06/04/2013 12:23 PM, Fabio Estevam wrote:
> When running the "save" command several times on a mx6qsabresd we see:
>
> U-Boot > save
> Saving Environment to MMC...
> Writing to MMC(1)... done
> U-Boot > save
> Saving Environment to MMC...
> MMC partition switch failed
...
> Fix this by making mmc->part_num to be in sync with CONFIG_SYS_MMC_ENV_PART
> after the partition has been changed in mmc_switch_part().
I deliberately didn't do this, because fini_mmc_for_env() passes the
value of mmc->part_num to call mmc_switch_part() in order to put things
back the way they were. This fix would break that. Can you investigate
why you're seeing the "MMC partition switch failed" message?
prev parent reply other threads:[~2013-06-04 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 18:23 [U-Boot] [PATCH] common: env_mmc: Make mmc->part_num in sync after a partition switch Fabio Estevam
2013-06-04 18:28 ` Stephen Warren [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=51AE31D9.3040502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox