[pkg-fso-maint] Bug#591604: uboot-envtools: fw_setenv refuses to set ethaddr, even though it can be set via uboot directly

[Vagrant Cascadian]

Control: tags -1 upstream moreinfo

On 2010-08-03, Daniel Kahn Gillmor wrote:
> when i try to use fw_setenv for the ethaddr variable on a Marvell
> guruplug, i get this error (mac address is anonymized):
>
> 0 root at moo:~# fw_setenv ethaddr 00:f0:43:XX:XX:XX
> Can't overwrite "ethaddr"
> 1 root at moo:~# 
>
> however, i'm able to reset the variable from the uboot bootloader directly:
...
> So the source for fw_setenv seems to be unnecessarily restrictive.

It may be because you were using a fw_setenv without any
platform-specific build options.

I'm wondering if using fw_setenv explicitly built for guruplug will work
any better. Version 2014.07+dfsg1-2 in jessie and
2014.10~rc2+dfsg1-2~exp1 in experimental ships a fw_printenv/fw_setenv
that is built specifically for each platform in
/usr/lib/u-boot/PLATFORM/fw_*. It seems some platforms may set values
for allowing this to be changed (ENV_FLAGS_VARACCESS_PREVENT_OVERWR and
ENV_FLAGS_VARACCESS_PREVENT_NONDEF_OVERWR in tools/env/fw_env.c), and a
build specifically for the guruplug may work for you.

I was planning on reverting back to a generic env tools build, though
I'd be curious if it works with a platform-specific build.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20141002/0de72177/attachment.sig>