From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtprelay01.ispgateway.de ([80.67.31.28]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1XLr1X-0007TH-GZ for ptxdist@pengutronix.de; Mon, 25 Aug 2014 11:57:15 +0200 Received: from [89.246.71.91] (helo=mail6.tqsc.de) by smtprelay01.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1XLr1W-0002ng-Uy for ptxdist@pengutronix.de; Mon, 25 Aug 2014 11:57:14 +0200 Received: from sc1209091.tqsc.de ([192.168.168.49] helo=[127.0.0.1]) by mail6.tqsc.de with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1XLr1W-0002ib-CA for ptxdist@pengutronix.de; Mon, 25 Aug 2014 11:57:14 +0200 Message-ID: <53FB0B71.4060409@tqsc.de> Date: Mon, 25 Aug 2014 12:09:53 +0200 From: Markus Niebel MIME-Version: 1.0 References: <1407140962-2116-1-git-send-email-bth@kamstrup.dk> <53E0CE18.9060103@tqsc.de> <20140808101639.GA11487@pengutronix.de> <915054555B5659448ACF8A70E114824D01402B42FA@Exchange2010.kamstrup.dk> In-Reply-To: <915054555B5659448ACF8A70E114824D01402B42FA@Exchange2010.kamstrup.dk> Subject: Re: [ptxdist] [RFC] u-boot-tools: emmc support in fw_printenv/fw_setenv Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de 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 /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 > 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