All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH : Fixes and enhancements for NAND flash.
Date: Sun, 27 Jul 2003 15:38:58 +0200	[thread overview]
Message-ID: <20030727133903.94069C602D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sun, 27 Jul 2003 08:20:06 CDT." <FD2AC9A020DDD51194710008C7089B200BEE2224@dlee17.itg.ti.com>

Dear Richard,

in message <FD2AC9A020DDD51194710008C7089B200BEE2224@dlee17.itg.ti.com> you wrote:
> 
> I do like the spinning wheel.  Is there any standard way to add a progress
> indicator into this or any code with significant delay?  Any of the users of

Use common sense. The only thing it does is making a part of the code
which takes more time than you like eveln  slower:  I'm  not  talking
about  the few CPU cycles for the printf (putc() would have been much
simpler), but especially about trashing the cache for "pretty" things
that don't add value, and the time it takes to output this stuff on a
slow serial line.

> the code I've talked with like such a feature.  It seems that same bit of
> code has been replicated in a few places. Surly having a library call and
> some ifdef's would be acceptable.

No, not at this place. It's a different story when -  for  example  -
waiting  for a flash sector be return to ready state when erasing it.
Here you have to wait anyway, so feel free  to  implement  this  busy
wait as you like it.

> As far a code formatting, I'll see if I can't fix it up.  I find myself
> using several editors depending on the context of what I'm doing.  I've not
> mastered any of them... When I do the diff -purN for the patch, I generally
> don't notice differences except in the areas I have changed something.  What
> code reformatter/filter do you use?  Some of the more recent u-boot releases
> have had a lot of style changes to the point I would suspect you ran
> something over the code.

vi and indent (indent -kr -i8 -bad -bap -nbc -br -c33 -cd33 -ncdb -ce
-ci8 -cli0 -cp33 -d0 -di1 -nfc1 -nfca -i4 -ip0 -l75  -lp  -pcs  -npsl
-nsc -nsob -nss -ts4, to be precise).


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
If something is different, it's either better or worse,  and  usually
both.                                                    - Larry Wall

  reply	other threads:[~2003-07-27 13:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-27 13:20 [U-Boot-Users] PATCH : Fixes and enhancements for NAND flash Woodruff, Richard
2003-07-27 13:38 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-27 16:30 Woodruff, Richard
2003-07-27 17:37 ` Wolfgang Denk
2003-07-27 17:53   ` Robert Schwebel
2003-07-27 18:25     ` Wolfgang Denk
2003-07-24 23:57 Woodruff, Richard
2003-07-26 21:35 ` Wolfgang Denk

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=20030727133903.94069C602D@atlas.denx.de \
    --to=wd@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.