From: Markus Niebel <list-09_ptxdist@tqsc.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC] u-boot-tools: emmc support in fw_printenv/fw_setenv
Date: Mon, 25 Aug 2014 12:09:53 +0200 [thread overview]
Message-ID: <53FB0B71.4060409@tqsc.de> (raw)
In-Reply-To: <915054555B5659448ACF8A70E114824D01402B42FA@Exchange2010.kamstrup.dk>
Hello Bruno,
> Yes, use the same U-Boot package for both bootloader and tools.
>
> Then we have the block device (emmc, etc.) vs. mtd[1] (NAND, NOR) support issue.
> As I see there are the following solutions:
> 1) Select fw_printenv/fw_setenv storage support based on define in board configuration, ex. CONFIG_ENV_IS_IN_MMC in mx28evk.
> 2) fw_printenv/fw_setenv support both storage technologies:
> a) Add storage type parameter to /etc/fw_env.config
> b) Autodetect storage type with strcmp() based on device name
>
As long as there is only one device for your platform, we should try to use the install_alternative method to install
a project specific /etc/fw_env.config from <BSP>/projectroot. If there are multiple locations for the environment a project specific way to set a link to the config file to be used has to be implemented in the root FS
>
>
> [1] MTD: Memory Technology Device, http://www.linux-mtd.infradead.org/faq/general.html
>
>
> Venlig hilsen / Best regards
>
> Kamstrup A/S <http://www.kamstrup.dk>
> Bruno Thomsen
> Development engineer
> Technology
>
> Kamstrup A/S
> Industrivej 28
> DK-8660 Skanderborg
> Tel: +45 89 93 10 00
> Fax: +45 89 93 10 01
> Dir: +45 89 93 13 94
> E-mail: bth@kamstrup.dk
> Web: www.kamstrup.dk
>
Best Regards
Markus Niebel
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-08-25 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 8:29 Bruno Thomsen
2014-08-05 11:37 ` Markus Niebel
2014-08-05 12:29 ` Markus Niebel
2014-08-08 10:16 ` Michael Olbrich
2014-08-20 9:02 ` Bruno Thomsen
2014-08-25 10:09 ` Markus Niebel [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=53FB0B71.4060409@tqsc.de \
--to=list-09_ptxdist@tqsc.de \
--cc=ptxdist@pengutronix.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