Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

[Vagrant Cascadian]

Control: tags 821056 patch pending

On 2016-04-17, Rick Thomas wrote:
> /usr/share/doc/u-boot-tools/examples/openrd.config
> # Configuration file for fw_(printenv/saveenv) utility.
> # Up to two entries are valid, in this case the redundant
> # environment sector is assumed present.
> #
> # XXX this configuration might miss a fifth parameter for the "Number of
> # sectors"
>
> # MTD device name   Device offset   Env. size   Flash sector size
> # Legacy u-boot versions:
> #/dev/mtd0   0xa 0x2 0x2
>
> # New u-boot versions:
> /dev/mtd0   0x6 0x2 0x2
>  cut here ===

Thanks!

Added to git, will be included in the next u-boot upload:

  
https://anonscm.debian.org/cgit/collab-maint/u-boot.git/commit/?id=0ee393e0eb5334da80ddc50e09f7873fb643651e

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

[Rick Thomas]

On Apr 17, 2016, at 8:35 AM, Vagrant Cascadian  wrote:

> On 2016-04-16, Rick Thomas wrote:
>> Re-reading this, I realize that I said “0x8” for the environment
>> location of legacy u-boot.  But when I went to test it, the true value
>> turned out to be “0xa”.
>> 
>> Sorry for the confusion.  The latter value (0xa) is correct.
> 
> Ok, what you submitted was:
> 
>>> # MTD device name   Device offset   Env. size   Flash sector size
>>> # Legacy u-boot versions:
>>> #/dev/mtd0   0xa 0x2 0x2
>>> 
>>> # New u-boot versions:
>>> /dev/mtd0   0x6 0x2 0x2
> 
> Are those the values you would like in the example fw_env.config for
> openrd, or are you saying they need to be adjusted? If those values need
> to be changed, please re-submit the example fw_env.config you would like
> included in the package.
> 
> 
> live well,
>  vagrant

The correct values for “Device offset” are:

0xa for “Legacy”  u-boot
   and
0x6 for “New”  u-boot

So my suggested /etc/fw_env.config for u-boot-tools on OpenRD machines is:

/usr/share/doc/u-boot-tools/examples/openrd.config
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
#
# XXX this configuration might miss a fifth parameter for the "Number of
# sectors"

# MTD device name   Device offset   Env. size   Flash sector size
# Legacy u-boot versions:
#/dev/mtd0   0xa 0x2 0x2

# New u-boot versions:
/dev/mtd0   0x6 0x2 0x2
 cut here ===

Sorry for any confusion I may have caused!

For completeness, my testing procedure was:

1) On an OpenRD Ultimate, running latest u-boot
(specifically, “U-Boot 2016.03+dfsg1-3 (Apr 04 2016 - 18:23:06 +)”)
I used the above file as is.
With it, I was able to read the u-boot environment from Linux with fw_printenv.
I did not try fw_setenv.

2) On an OpenRD Client, running a legacy u-boot
(specifically. “U-Boot 1.1.4 (May 18 2009 - 13:33:10) Marvell version: 3.4.16”)
I reversed the commenting on the two “/dev/mtd0” lines.
With that, I was able to read the u-boot environment from Linux with 
fw_printenv.
I did not try fw_setenv.

For the time being, I plan to leave the Client machine with the legacy u-boot, 
incase
you find that further testing is required.

Thank you for your efforts!

Rick

Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

[Vagrant Cascadian]

On 2016-04-16, Rick Thomas wrote:
> Re-reading this, I realize that I said “0x8” for the environment
> location of legacy u-boot.  But when I went to test it, the true value
> turned out to be “0xa”.
>
> Sorry for the confusion.  The latter value (0xa) is correct.

Ok, what you submitted was:

>> # MTD device name   Device offset   Env. size   Flash sector size
>> # Legacy u-boot versions:
>> #/dev/mtd0   0xa 0x2 0x2
>> 
>> # New u-boot versions:
>> /dev/mtd0   0x6 0x2 0x2

Are those the values you would like in the example fw_env.config for
openrd, or are you saying they need to be adjusted? If those values need
to be changed, please re-submit the example fw_env.config you would like
included in the package.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

[Rick Thomas]

Re-reading this, I realize that I said “0x8” for the environment location 
of legacy u-boot.  But when I went to test it, the true value turned out to be 
“0xa”.

Sorry for the confusion.  The latter value (0xa) is correct.

Rick

PS:  Just out of curiosity, was there a reason behind the change?  Or was it 
just one of those things that “seemed like a good idea at the time” ?

On Apr 16, 2016, at 6:04 PM, Rick Thomas  wrote:

> 
> On Apr 15, 2016, at 12:29 PM, Vagrant Cascadian  wrote:
> 
>> On 2016-04-14, Rick Thomas wrote:
>>> The directory /usr/share/doc/u-boot-tools/examples/ has example .config 
>>> files
>>> for a variety of devices, but none for the OpenRD base, client or ultimate.
>> ...
>>> Oh, and BTW, the lastest u-boot puts the environment at 0x6, while 
>>> legacy
>>> versions put it at 0x8, so it would be nice to reflect that (as was
>>> done for sheevaplug -- thanks!) in the example .config file. 
>> 
>> If you could provide a tested, working config, I can include it, but I
>> have no way of testing it myself.
>> 
>> 
>> live well,
>> vagrant
> 
> Here you go:
> 
> /usr/share/doc/u-boot-tools/examples/openrd.config
> # Configuration file for fw_(printenv/saveenv) utility.
> # Up to two entries are valid, in this case the redundant
> # environment sector is assumed present.
> #
> # XXX this configuration might miss a fifth parameter for the "Number of
> # sectors"
> 
> # MTD device name   Device offset   Env. size   Flash sector size
> # Legacy u-boot versions:
> #/dev/mtd0   0xa 0x2 0x2
> 
> # New u-boot versions:
> /dev/mtd0   0x6 0x2 0x2
>  cut here ===
> 
> Tested and working on openrd client and ultimate hardware for both versions 
> of u-boot:
> Legacy: U-Boot 1.1.4 (May 18 2009 - 13:33:10) Marvell version: 3.4.16
> New: U-Boot 2016.03+dfsg1-3 (Apr 04 2016 - 18:23:06 +)
> 
> Rick Thomas
> 
> PS: You may add my name as a tester if you want.

Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

[Rick Thomas]

On Apr 15, 2016, at 12:29 PM, Vagrant Cascadian  wrote:

> On 2016-04-14, Rick Thomas wrote:
>> The directory /usr/share/doc/u-boot-tools/examples/ has example .config files
>> for a variety of devices, but none for the OpenRD base, client or ultimate.
> ...
>> Oh, and BTW, the lastest u-boot puts the environment at 0x6, while legacy
>> versions put it at 0x8, so it would be nice to reflect that (as was
>> done for sheevaplug -- thanks!) in the example .config file. 
> 
> If you could provide a tested, working config, I can include it, but I
> have no way of testing it myself.
> 
> 
> live well,
>  vagrant

Her you go:

/usr/share/doc/u-boot-tools/examples/openrd.config
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
#
# XXX this configuration might miss a fifth parameter for the "Number of
# sectors"

# MTD device name   Device offset   Env. size   Flash sector size
# Legacy u-boot versions:
#/dev/mtd0   0xa 0x2 0x2

# New u-boot versions:
/dev/mtd0   0x6 0x2 0x2
 cut here ===

Tested and working on openrd client and ultimate hardware for both versions of 
u-boot:
Legacy: U-Boot 1.1.4 (May 18 2009 - 13:33:10) Marvell version: 3.4.16
New: U-Boot 2016.03+dfsg1-3 (Apr 04 2016 - 18:23:06 +)

Rick Thomas

PS: You may add my name as a tester if you want.

Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

[Vagrant Cascadian]

On 2016-04-14, Rick Thomas wrote:
> The directory /usr/share/doc/u-boot-tools/examples/ has example .config files
> for a variety of devices, but none for the OpenRD base, client or ultimate.
...
> Oh, and BTW, the lastest u-boot puts the environment at 0x6, while legacy
> versions put it at 0x8, so it would be nice to reflect that (as was
> done for sheevaplug -- thanks!) in the example .config file. 

If you could provide a tested, working config, I can include it, but I
have no way of testing it myself.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#821056: u-boot-tools: no example /etc/fw_env.config files for openrd devices

[Rick Thomas]

Package: u-boot-tools
Version: 2016.03+dfsg1-3
Severity: normal

Dear Maintainer,

The directory /usr/share/doc/u-boot-tools/examples/ has example .config files
for a variety of devices, but none for the OpenRD base, client or ultimate.

Until recently, this was not a roblem because recent versions of u-boot did not
support the OpenRD devices.

But as of version 2016.03+dfsg1-3, there is full u-boot support for OpenRD
and u-boot-tools needs to reflect that fact.

Oh, and BTW, the lastest u-boot puts the environment at 0x6, while legacy
versions put it at 0x8, so it would be nice to reflect that (as was
done for sheevaplug -- thanks!) in the example .config file. 

Enjoy!


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 4.4.0-1-marvell
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages u-boot-tools depends on:
ii  libc6  2.22-5

u-boot-tools recommends no packages.

u-boot-tools suggests no packages.

-- no debconf information