From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Date: Thu, 11 Jan 2018 12:16:40 +0000
Subject: [U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09
In-Reply-To: <20180111114453.E951F240141@gemini.denx.de>
References: <0B2EBCD48D33654381E736352034C70C01B64CD6@dor-sms-xch01.digi.com>
 <20180111100422.7957c7f3@jawa> <20180111114453.E951F240141@gemini.denx.de>
Message-ID: <1515672997.18795.20.camel@infinera.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Thu, 1970-01-01 at 00:00 +0000, Wolfgang Denk wrote:
> 
> Hello,
> 
> In message <20180111100422.7957c7f3@jawa> you wrote:
> > 
> > > I am using U-Boot 2015.04, and the new root file system for my
> > > platform includes u-boot-fw-utils 2017.09. I have noticed that
> > > fw_{print,set}env utilities are no longer working.
> > 
> > Strace output would be helpful here....
> 
> Definitely.  Ideally both for the old, working, and for the new,
> failing, version.
> 
> > The fw_* utils were a bit reworked around 2017.09 (there were some
> > build breaks of it IIRC), so yes you may see some problems.
> 
> But then, the actual format of the environment data has never been
> changed, so we really need more details.

Speaking of the fw tools, I have always wanted to be able to specify
"whole mtd device" for plain NOR flash in fw_env.config so instead of 
 /dev/mtd1		0x0000		0x4000		0x4000
One could jsut say 
 /dev/mtd1		0x0000		0x4000
like one can do for SPI flash. Thoughts ?

 Jocke