Stefan Roese wrote: > On Friday 07 March 2008, Clemens Koller wrote: >> ACK from my side to Jerry's version. Maybe a quite long fixed length (~40 >> characters) bar would also be reasonable and the dot-time scaled to fit the >> progress. >> >> A progress bar needs IMO two informations: >> - that it's still working... so a quite frequent output of something to >> keep me calm. - how long it will take... so I know how much time I will >> have to get the next cup of coffee to keep me tickin'. >> >> Perfect (= close to overkill, I know) would be IMO an additional output >> like: >> >> Programming Flash from 0xc0ldbeef to 0xc0ldcafe takes 112s. >> ................. | >> >> So, I don't need to estimate from the first dots how long it will take to >> complete. > > I don't think printing the programming time/speed at beginning of the > operation is doable. At least not without bigger changes. But an output at > end of the operation like: > > Wrote 512kB in 5.4 seconds (94,8 kB/s) > > would be nice. This way the developer could see, if the interface to the > FLASH > chips is optimized. But I think this is overkill too. Let's concentrate on a > clean progress bar with a fixed length. > > Patches welcome. :) > > Best regards, > Stefan
All but the timing part ;-) <http://article.gmane.org/gmane.comp.boot-loaders.u-boot/37626> Best regards, gvb ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
