[U-Boot] [PATCH 2/3] Automatic software update from TFTP server

[Wolfgang Denk]

Dear Bartlomiej Sieka,

In message <48DB5EC3.8000604 at semihalf.com> you wrote:
>
> > I see. Maybe we should call the variable "updatefile" or similar,
> > then?
> 
> How about "au_file"? "updatefile" suffers from similarity to the
> commonly used (although not documented) "update" env. variable. But I'm
> fine either way, just let me know what you prefer.

I would use "updatefile", but if you prefer "au_file" (and nobody
else comes up with comments or better suggestions) that's fine with
me, too.

> > So you will either have to add some  more  #ifdef's,  or  think  what
> > could  happen  if the VFD (Vacuum Fluorescent Display) initialization
> > code runs first - I would not expect any negative impact?
> 
> I don't think there will be any negative impact per se, the update
> procedure will just start a bit later (the time needed to display the
> bitmap on the FVD).

Actually that would prebably be wanted, as the  end  user  would  see
that  the system was powered on [and actually we don't really have to
care much, as the TRAB board has reached EOL officially].

> Will move au_tftp() call till after the VFD stuff.

Thanks.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
It all seemed, he thought, to be rather a lot of  trouble  to  go  to
just sharpen a razor blade.  - Terry Pratchett, _The Light Fantastic_