u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] env_mmc: make board configurable the partition for the environment
Date: Fri, 17 Jan 2014 12:34:04 -0700	[thread overview]
Message-ID: <52D985AC.2010702@wwwdotorg.org> (raw)
In-Reply-To: <1389950098-18122-1-git-send-email-hector.palacios@digi.com>

On 01/17/2014 02:14 AM, Hector Palacios wrote:
> This complements commit 9404a5fc7cb58 "env_mmc: allow environment to be
> in an eMMC partition" by allowing boards to accommodate the partition
> to use for the environment in different scenarios (similarly to what is
> done with the mmc dev number). Depending on the detected boot media,
> boards may decide to store the environment in a different partition.
> 
> The __weak function also allows to remove some ifdefs from the code.
> If CONFIG_SYS_MMC_ENV_PART is not defined, partition 0 is assumed
> (default value for U-Boot when a partition is not provided).

> diff --git a/common/env_mmc.c b/common/env_mmc.c

>  __weak int mmc_get_env_devno(void)
>  {
>  	return CONFIG_SYS_MMC_ENV_DEV;
> +
> +#if !defined(CONFIG_SYS_MMC_ENV_PART)

Isn't the trailing } for that function missing?

> +#define CONFIG_SYS_MMC_ENV_PART 0
> +#endif
> +
> +__weak int mmc_get_env_partno(void)
> +{
> +	return CONFIG_SYS_MMC_ENV_PART;
>  }

      parent reply	other threads:[~2014-01-17 19:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17  9:14 [U-Boot] [PATCH v2 1/2] env_mmc: make board configurable the partition for the environment Hector Palacios
2014-01-17  9:14 ` [U-Boot] [PATCH v2 2/2] env_mmc: default to 0 if CONFIG_SYS_MMC_ENV_DEV not defined Hector Palacios
2014-01-17 10:51   ` Otavio Salvador
2014-01-17 19:35   ` Stephen Warren
2014-01-17 10:50 ` [U-Boot] [PATCH v2 1/2] env_mmc: make board configurable the partition for the environment Otavio Salvador
2014-01-17 19:34 ` 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=52D985AC.2010702@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;
as well as URLs for NNTP newsgroup(s).