On 05/26/15 13:35, Vagrant Cascadian wrote:
On 2015-05-26, Rick Thomas wrote:
On May 26, 2015, at 12:44 PM, Rick Thomas <rbtho...@pobox.com> wrote:
On May 26, 2015, at 10:32 AM, Vagrant Cascadian <vagr...@aikidev.net> wrote:
On 2015-05-26, Rick Thomas wrote:
The entry committed may not work with older versions of u-boot, as some
of the device offsets in the cubox-i support included in mainline
u-boot, and the patches in 2015.04+ in debian are based on mainline
u-boot.
...
Thanks! Would it be possible to include in the comments some reference to the
minimum level
of uboot for which it is applicable?
Sure.
I installed the file in that URL as /etc/fw_env.config and when I run
fw_printenv, it says
Warning: Bad CRC, using default environment
and prints only a few lines. I was expecting to see the many-line printout I
get when
I do âprintenvâ in u-boot.
Is this expected behavior?
It is if you're running the default environment and haven't saved your
environment to the mmc (e.g. saveenv from the u-boot prompt).
Iâm running uboot version 2015.04+dfsg1-2
That's the right version...
In general I prefer to work with the default environment, as I'm often
testing new u-boot versions and want to make sure it continues to work
with the defaults, and it can be tricky to remember to reset the default
environment.
live well,
vagrant
Thanks for the explanation. I wasn't aware that there were two
environments. Is this explained somewhere? I'd love to RTFM if I only
knew where the FM was!
I assume, if I do "saveenv" in uboot, that I'll make the two
environments equal and see the same thing from fw_printenv in Linux as I
do from printenv in u-boot? Is this correct?
... I tried it and that's what happened. Thanks!
Enjoy!
Rick
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
