From: Artem Bityutskiy <dedekind1@gmail.com>
To: Darwin Rambo <drambo@broadcom.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBI - disable subpage verify and use CONFIG_MTD_NAND_VERIFY_WRITE possible?
Date: Wed, 28 Apr 2010 16:47:17 +0300 [thread overview]
Message-ID: <1272462437.7750.37.camel@localhost> (raw)
In-Reply-To: <B125D8217ABC4B43826503DE00A2D44910FDDFB4E6@SJEXCHCCR01.corp.ad.broadcom.com>
Hi,
On Mon, 2010-04-19 at 17:52 -0700, Darwin Rambo wrote:
> Hello Artem,
>
> Can you please clarify something for me?
>
> http://www.linux-mtd.infradead.org/faq/ubi.html#L_subpage_verify_fail
>
> I read this note and still, CONFIG_MTD_NAND_VERIFY_WRITE is very
> useful for me.
Ok.
> The question is, if I don't mind wasting a bit of flash, and
> configure UBI to not do subpage writes and put the EC and VID headers
> on separate pages (for example ubi.mtd=6,4096), does UBI then always
> do page writes and would CONFIG_MTD_NAND_VERIFY_WRITE then work
> reliably for me?
Yes, in this case UBI will never use sub-pages, all writes will be 4KiB
aligned, and the feature should work.
> Or are there other places in the code that might do subpage writes?
No.
> So far it seems to work well for me with the verify on and no
> subpages for the headers.
Right.
> By the way, the standard nand_verify_buf() function in nand_base.c
> uses readb(chip->IO_ADDR_R) and doesn't use something like
> chip->ecc.read_page() to correct the data so this sounds like a bug to
> me.
Yup. I think this feature was not used by anyone for long time.
> But I override this to do corrected reads anyways, which works better
> for SLC/MLC flash which can show one or more bit errors in a page
> read.
Just send a patch then :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-04-28 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 0:52 UBI - disable subpage verify and use CONFIG_MTD_NAND_VERIFY_WRITE possible? Darwin Rambo
2010-04-28 13:47 ` Artem Bityutskiy [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=1272462437.7750.37.camel@localhost \
--to=dedekind1@gmail.com \
--cc=drambo@broadcom.com \
--cc=linux-mtd@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;
as well as URLs for NNTP newsgroup(s).