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 09:36:49 -0500 [thread overview]
Message-ID: <47D15301.8060601@ge.com> (raw)
In-Reply-To: <20080307141357.3276E247B3@gemini.denx.de>
Wolfgang Denk wrote:
> In message <47D149CA.8010205@ge.com> you wrote:
>> The saveenv also looks funky. I only mucked with the cmd_mem.c command
>> to make it display better with the progress dots, obviously the saveenv
>> command needs to have the same changes
>> s/"Writing to Flash... "/"Writing to Flash\n"/
>
> Please don't.
>
> That shall not become a 200 lines output. Please keep this on a single
> line.
>
> It makes no sense to have all useful information srolling out of
> sight all too quickly just for such bells and whistles.
>
> Best regards,
> Wolfgang Denk
I was too terse. The problem is that I added a progress bar.
Previously, the printout sequence was:
Writing to Flash...
followed by an indeterminate wait, followed by the string "done." which
formed the composite:
Writing to Flash... done.
I added a progress bar, but the progress bar needs to be on a new line.
I fixed this in cmd_mem.c, but not in the env code, resulting in
Stefan's complaint (b).
With the (next version of the) progress dots patch, the sequence will be:
Writing to Flash
v
..................................................
done.
One thing I am debating is to add a parameter to the flash write command
that says whether to do the progress dots or not. Then we could
suppress the (silly) dots on short writes.
Best regards,
gvb
next prev parent reply other threads:[~2008-03-07 14:36 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
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 [this message]
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=47D15301.8060601@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