From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] [OneNAND] Flex-OneNAND boundary settings
Date: Thu, 5 Nov 2009 17:08:27 -0600 [thread overview]
Message-ID: <20091105230827.GB13402@loki.buserror.net> (raw)
In-Reply-To: <C8B0D89A196544F388B778388D549E61@sisodomain.com>
On Wed, Nov 04, 2009 at 10:39:41AM +0530, Amul Kumar Saha wrote:
> while (blocks) {
> + blocksize = onenand_blocksize(ofs);
> +
> ret = mtd->block_isbad(mtd, ofs);
> if (ret) {
> printk("Bad blocks %d at 0x%x\n",
> - (u32)(ofs >> this->erase_shift), (u32)ofs);
> + (u32)onenand_block(this, ofs), (u32)ofs);
This isn't new, but %d doesn't match u32 (though I guess GCC doesn't
complain about signedness) -- and we shouldn't be chopping off the upper
bits of ofs.
> + blocks = (int) onenand_block(this, ofs + len)
> + - onenand_block(this, ofs);
Unnecessary cast.
> @@ -493,9 +531,11 @@ U_BOOT_CMD(
> "onenand write[.oob] addr off size\n"
> " read/write 'size' bytes starting at offset 'off'\n"
> " to/from memory address 'addr', skipping bad blocks.\n"
> - "onenand erase [force] [off size] - erase 'size' bytes from\n"
> + "onenand erase [force] [off size] - erase 'size' bytes from off\n"
> "onenand test [off size] - test 'size' bytes from\n"
> " offset 'off' (entire device if not specified)\n"
> "onenand dump[.oob] off - dump page\n"
> "onenand markbad off [...] - mark bad block(s) at offset (UNSAFE)"
> + "onenand setboundary DIE BOUNDARY [LOCK] - \n"
> + "Change SLC boundary of Flex-OneNAND\n"
Description should be indented if you're going to put it on a new line.
-Scott
next prev parent reply other threads:[~2009-11-05 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 6:13 [U-Boot] [PATCH 3/3] [OneNAND] Flex-OneNAND boundary settings Amul Kumar Saha
2009-11-04 5:09 ` Amul Kumar Saha
2009-11-05 23:08 ` Scott Wood [this message]
2009-11-06 11:43 ` Amul Kumar Saha
2009-11-06 11:47 ` Amul Kumar Saha
2009-11-09 20:02 ` Scott Wood
2009-11-11 5:56 ` Amul Kumar Saha
2009-11-11 5:57 ` Amul Kumar Saha
2009-11-16 22:56 ` Wolfgang Denk
2009-11-19 11:14 ` Amul Kumar Saha
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=20091105230827.GB13402@loki.buserror.net \
--to=scottwood@freescale.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 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.