From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Aring <alex.aring@googlemail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/8] improve nandtest command
Date: Tue, 23 Oct 2012 08:27:49 +0200 [thread overview]
Message-ID: <20121023062749.GG27665@pengutronix.de> (raw)
In-Reply-To: <1350890612-10588-1-git-send-email-alex.aring@gmail.com>
On Mon, Oct 22, 2012 at 09:23:24AM +0200, Alexander Aring wrote:
> Small Summary:
> - The old nandtest do a ecc statistic per eraseblock, it's better to
> do this per page. I don't know how this works with subpages.
>
> - Add a progressbar instead of prints of current flash offset.
>
> - Rename command argument 'passes' to 'iterations', which makes more
> sense.
>
> - use builtin function 'get_random_bytes' to generate random buffer.
>
> - use loff_t instead of off_t. To handle flash >4GB.
>
> - add another constraints check for writesize.
Applied, thanks
Sascha
>
> Alexander Aring (8):
> nandtest: stat ecc per page not per eraseblock
> nandtest: add progressbar instead of offset print
> nandtest: rename command argument p to i
> nandtest: change flash length variable type
> nandtest: use get_random_bytes instead of for loop
> nandtest: clean up code
> nandtest: use loff_t instead off_t
> nandtest: add another constraints check
>
> commands/nandtest.c | 190 ++++++++++++++++++++++++++++------------------------
> 1 file changed, 103 insertions(+), 87 deletions(-)
>
> --
> 1.7.12.4
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-10-23 6:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 7:23 Alexander Aring
2012-10-22 7:23 ` [PATCH 1/8] nandtest: stat ecc per page not per eraseblock Alexander Aring
2012-10-22 7:23 ` [PATCH 2/8] nandtest: add progressbar instead of offset print Alexander Aring
2012-10-22 7:23 ` [PATCH 3/8] nandtest: rename command argument p to i Alexander Aring
2012-10-22 7:23 ` [PATCH 4/8] nandtest: change flash length variable type Alexander Aring
2012-10-22 7:23 ` [PATCH 5/8] nandtest: use get_random_bytes instead of for loop Alexander Aring
2012-10-22 7:23 ` [PATCH 6/8] nandtest: clean up code Alexander Aring
2012-10-22 7:23 ` [PATCH 7/8] nandtest: use loff_t instead off_t Alexander Aring
2012-10-22 7:23 ` [PATCH 8/8] nandtest: add another constraints check Alexander Aring
2012-10-23 6:27 ` Sascha Hauer [this message]
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=20121023062749.GG27665@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=alex.aring@googlemail.com \
--cc=barebox@lists.infradead.org \
/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