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: > >> Control: tags -1 +pending >> >> On 2015-05-26, Rick Thomas wrote: >>> When I try fw_printenv on my cubox i4Pro, it complains >>> Cannot parse config file: No such file or directory >>> >>> Looking in >>> /usr/share/doc/u-boot-tools/examples/ >>> there are several example .config files, but none for the cubox machines. >>> >>> Could you please provide one? >> >> Committed to git: >> >> https://anonscm.debian.org/cgit/collab-maint/u-boot.git/commit/?id=b8e4763e5d920ad8dcacc1d51231647f7fddbf83 >> >> Will include it in the next upload. >> >> 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. >> >> >> live well, >> vagrant > > Thanks! Would it be possible to include in the comments some reference to > the minimum level > of uboot for which it is applicable? Hmmm… 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? I’m running uboot version 2015.04+dfsg1-2 Enjoy! Rick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
