On Wed, 29 Mar 2017, Wolfgang Denk wrote:
> Dear Robert,
>
> In message <alpine.lfd.2.20.1703290927110.21...@uk63952.mitel.com> you wrote:
> >
> > kind of a trivial question but i was just perusing the code related
> > to FIT images and ran across this in main.c:
> ...
> > #if defined(CONFIG_UPDATE_TFTP)
> > update_tftp(0UL, NULL, NULL); <----- THERE
> > #endif /* CONFIG_UPDATE_TFTP */
> > ... snip ...
> >
> > i'm assuming that, given the proper configuration, u-boot will try
> > to update its own binary on every single boot, yes? not sure why i
> > never noticed that before.
>
> This is documented in the "README" and especially in the
> "doc/README.update" files. It also describes how one would normally
> use the "updatefile" environment variable to enable / disable this
> feature. But yes, if you keep this vaiable around, this will repeat
> on every boot, according to good old UNIX philosophy:
>
> "UNIX was not designed to stop you from doing stupid things, because
> that would also stop you from doing clever things." - Doug Gwyn
yup, i eventually found that README.update file, this behaviour is
just fine for what i'm doing, thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
