From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] New NAND subsystem: mtd like commands support jffs2 and bad blocks
Date: Tue, 10 Oct 2006 12:14:00 +0200 [thread overview]
Message-ID: <200610101214.01247.sr@denx.de> (raw)
In-Reply-To: <5c01f02f0610090947x7b7b9c1fjfc6efa787963d7c0@mail.gmail.com>
Hi Guido,
On Monday 09 October 2006 18:47, Guido Classen wrote:
> now the next try...
;-)
> > Hmmm. Not sure here. Perhaps you could try to enhance the output so that
> > it there printend that much output.
>
> The relation between time spent on NAND operation and progress output may
> depend on much things like NAND type and size, CPU and bus speeds, console
> type and speed. So I have changed the patch in a way that the output is
> only print for whole percent steps. This should reduce the output at
> reasonable amount independent from this circumstances.
Looks much better to me. Thanks.
> > And I also noticed that the output is not
> > correct:
> >
> > => nand erase 0 1000000
> >
> > NAND erase: device 0 offset 0x0, size 0x1000000
> > Erasing 128 Kibyte at fe0000 -- 1% complete.
> > OK
> >
> > The 1% is for the complete FLASH size, but I was erasing just a small
> > part of it. I would really like to see 100%, even when erasing a small
> > part.
>
> This is fixed
Good. Thanks.
> > > Maybe a "quiet" option at command line for the related commands (like
> > > "clean" option) will be the right way to do it. What do you think about
> > > this?
> > >
> > > I will rework the patch with your suggestions as soon as provisions to
> > > switch on/off the "quiet" option and resubmit it the next days.
> >
> > Please see my comment above. I don't want the commands to become too
> > complex with lots of options (they are already complex enough). So my
> > suggestion is to change the code that it doesn't slow down the operation
> > anymore.
>
> Now I consider an environment variable "quiet" if set for activating the
> quiet options. This even permits the usage of the quiet option with macros.
> To my mind this is a very convenient to apply the option to a sequence of
> NAND operations.
Good idea. So the "normal" operation with "quiet" not set will give the
complete output including the "Skipping bad block..." lines.
> Furthermore the spelling and grammar fixes from Phil are applied! Phil
> thank you very much for that!
Thanks.
If Wolfgang has no further issues we will commit your patch in the next few
days. Thanks again.
Best regards,
Stefan
next prev parent reply other threads:[~2006-10-10 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5c01f02f0610060802o429760efib1ccc8c936f4509a@mail.gmail.com>
2006-10-06 15:09 ` [U-Boot-Users] [PATCH] New NAND subsystem: mtd like commands support jffs2 and bad blocks Guido Classen
2006-10-07 10:35 ` Stefan Roese
2006-10-07 14:20 ` Guido Classen
2006-10-08 10:26 ` Stefan Roese
2006-10-08 13:49 ` Guido Classen
2006-10-09 7:49 ` Stefan Roese
2006-10-09 16:47 ` Guido Classen
2006-10-10 10:14 ` Stefan Roese [this message]
2006-10-10 13:05 ` Ladislav Michl
2006-10-10 17:03 ` Guido Classen
2006-10-12 5:20 ` Stefan Roese
2006-10-12 8:48 ` Guido Classen
2006-10-12 9:08 ` Wolfgang Denk
2006-10-07 18:56 ` 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=200610101214.01247.sr@denx.de \
--to=sr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox