From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Add flash programming counter]
Date: Fri, 07 Mar 2008 08:26:49 -0500 [thread overview]
Message-ID: <47D14299.4090609@ge.com> (raw)
In-Reply-To: <200803071411.57287.sr@denx.de>
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
next prev parent reply other threads:[~2008-03-07 13:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 19:43 [U-Boot-Users] [PATCH] Add flash programming counter] York Sun
2008-03-06 6:20 ` Stefan Roese
2008-03-06 8:19 ` Martin Krause
2008-03-06 12:48 ` Wolfgang Denk
2008-03-06 13:33 ` Stefan Roese
2008-03-06 16:32 ` Wolfgang Denk
2008-03-06 17:17 ` Michael Schwingen
2008-03-06 19:35 ` Jerry Van Baren
2008-03-07 13:02 ` Clemens Koller
2008-03-07 13:11 ` Stefan Roese
2008-03-07 13:26 ` Jerry Van Baren [this message]
2008-03-07 13:35 ` Stefan Roese
2008-03-07 13:57 ` Jerry Van Baren
2008-03-07 14:04 ` Stefan Roese
2008-03-07 14:15 ` Wolfgang Denk
2008-03-07 14:18 ` Kumar Gala
2008-03-07 14:22 ` Stefan Roese
2008-03-07 14:13 ` Wolfgang Denk
2008-03-07 14:36 ` Jerry Van Baren
2008-03-07 14:59 ` Wolfgang Denk
2008-03-07 16:09 ` Jerry Van Baren
2008-03-07 16:33 ` Wolfgang Denk
2008-03-07 17:12 ` Jerry Van Baren
2008-03-07 19:36 ` Wolfgang Denk
2008-03-07 20:52 ` Jerry Van Baren
2008-03-07 17:46 ` Kim Phillips
2008-03-07 19:39 ` Wolfgang Denk
2008-03-07 14:10 ` Wolfgang Denk
2008-03-07 13:24 ` Jerry Van Baren
2008-03-07 13:33 ` Jerry Van Baren
2008-03-06 19:41 ` Stefan Roese
2008-03-06 22:58 ` Wolfgang Denk
2008-03-07 6:38 ` Stefan Roese
2008-03-07 16:34 ` Jon Loeliger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47D14299.4090609@ge.com \
--to=gerald.vanbaren@ge.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox