From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv3] arm: socfpga: Enable saveenv for SD/MMC
Date: Wed, 23 Sep 2015 21:37:19 +0200 [thread overview]
Message-ID: <201509232137.19568.marex@denx.de> (raw)
In-Reply-To: <1443036108-24630-1-git-send-email-dinguyen@opensource.altera.com>
On Wednesday, September 23, 2015 at 09:21:48 PM, dinguyen at opensource.altera.com
wrote:
> From: Dinh Nguyen <dinguyen@opensource.altera.com>
>
> Enable the able to save the environment variables when SD/MMC is used.
>
> Signed-off-by: Dinh Nguyen <dinguyen@opensource.altera.com>
> ---
> v3: Only define ENV_IS_NOWHERE if env is not in MMC, NAND, FAT, and
> SPI_FLASH v2: Move this option to be on a per-board basis
> Add config for socfpga_cyclone5 and socfpga_arria5
> ---
[...]
Hi!
> --- a/include/configs/socfpga_common.h
> +++ b/include/configs/socfpga_common.h
> @@ -281,7 +281,12 @@ unsigned int cm_get_qspi_controller_clk_hz(void);
> #define CONFIG_SYS_CONSOLE_IS_IN_ENV
> #define CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE
> #define CONFIG_SYS_CONSOLE_ENV_OVERWRITE
> +#if !defined CONFIG_ENV_IS_IN_MMC && \
> + !defined CONFIG_ENV_IS_IN_NAND && \
> + !defined CONFIG_ENV_IS_IN_FAT && \
> + !defined CONFIG_ENV_IS_IN_SPI_FLASH
This really doesn't scale, I can have env in UBI for example, or on EEPROM
and this condition would trigger and cause a problem. Just move the
CONFIG_ENV_IS_NOWHERE into the respective board files and be done with it.
This bit of duplication is pretty OK I'd say.
> #define CONFIG_ENV_IS_NOWHERE
> +#endif
> #define CONFIG_ENV_SIZE 4096
>
> /*
[...]
Sorry to pester you this way, the rest is great of course :)
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-09-23 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 19:21 [U-Boot] [PATCHv3] arm: socfpga: Enable saveenv for SD/MMC dinguyen at opensource.altera.com
2015-09-23 19:37 ` Marek Vasut [this message]
2015-09-24 17:47 ` Pavel Machek
2015-09-24 17:51 ` Marek Vasut
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=201509232137.19568.marex@denx.de \
--to=marex@denx.de \
--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