public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09
Date: Thu, 11 Jan 2018 12:16:40 +0000	[thread overview]
Message-ID: <1515672997.18795.20.camel@infinera.com> (raw)
In-Reply-To: <20180111114453.E951F240141@gemini.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
 

  parent reply	other threads:[~2018-01-11 12:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 11:17 [U-Boot] U-Boot 2015 and u-boot-fw-utils 2017.09 Diaz
2018-01-11  9:04 ` Lukasz Majewski
2018-01-11 11:44   ` Wolfgang Denk
2018-01-11 11:58     ` Diaz
2018-01-11 12:31       ` Lukasz Majewski
2018-01-11 12:16     ` Joakim Tjernlund [this message]
2018-01-11 12:33       ` Lukasz Majewski

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=1515672997.18795.20.camel@infinera.com \
    --to=joakim.tjernlund@infinera.com \
    --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