Your message dated Wed, 20 Apr 2016 16:22:45 -0700
with message-id <[email protected]>
and subject line Re: Bug#812395: u-boot-tools: sheevaplug /etc/fw_env.config -
explain how env address depends on your version of u-boot.
has caused the Debian Bug report #812395,
regarding u-boot-tools: sheevaplug /etc/fw_env.config - explain how env address
depends on your version of u-boot.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
812395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812395
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: u-boot-tools
Version: 2016.01+dfsg1-1
Severity: wishlist
I believe the following to be true based on experiments with my two
sheevaplugs:
If your Sheevaplug has a u-boot version prior to 2014.10+dfsg1-5,
including any of the original "Marvell" versions, the environment is
located at 0x60000 and this should be reflected in the "Device offset"
field in the /etc/fw_env.config file.
If your Sheevaplug has a u-boot version of 2014.10+dfsg1-5, e.g. if
you upgraded u-boot while running Debian Jessie, or 2016.01+dfsg1-1
or later from Debian Stretch or later, the environment is located at
0x80000 and this should, in turn, be reflected in the "Device offset"
field in the /etc/fw_env.config file.
I theorize that the reason for this is that versions of the u-boot.kwb
binary prior to 2014.10 were shorter than 0x60000 (three erase pages
in the MTD flash), so it made sense to locate the environment at the
beginning of the fourth erase page, 0x60000.
But with the 2014.10 version and later, the u-boot.kwb binary had grown
and now encroached upon part of the fourth erase page. This meant that
the environment had to move up one erase page to 0x80000.
If this is correct, it needs to be reflected in
/usr/share/doc/u-boot-tools/examples/sheevaplug.config so that users
can configure /etc/fw_env.config correctly for their particular machines.
If a similar analysis applies to other arm devices that use u-boot
(I don't know whether it does), then it might be appropriate to put
it in a README file in the /usr/share/doc/u-boot-tools/examples
directory. A pointer to that README should go in
/usr/share/doc/u-boot-tools/examples/*.config, as appropriate for
affected devices.
Thanks!
-- System Information:
Debian Release: stretch/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: armel (armv5tel)
Kernel: Linux 4.3.0-1-kirkwood
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.21-6
u-boot-tools recommends no packages.
u-boot-tools suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2016.01+dfsg1-1
On 2016-04-18, Rick Thomas wrote:
>>> If you could please provide a patch detailing exactly what you would
>>> like changed, that would be appreciated.
>
> It look like the latest u-boot-tools has exactly what I would have
> said. Very sorry for taking so long to get back.
>
> I think this bug can be closed now.
Ok, doing so!
live well,
vagrant
signature.asc
Description: PGP signature
--- End Message ---
