From: Matthieu CASTET <matthieu.castet@parrot.fr>
To: linux-mtd@lists.infradead.org
Subject: Re: 2.6.20 : BUG in nand_do_read_oobwith MTD_OOB_PLACE ?
Date: Thu, 15 Feb 2007 15:37:54 +0000 (UTC) [thread overview]
Message-ID: <loom.20070215T163517-47@post.gmane.org> (raw)
In-Reply-To: loom.20070209T155657-545@post.gmane.org
Matthieu CASTET <matthieu.castet <at> parrot.fr> writes:
>
> Hi,
>
> 2.6.20 nand mtd seems to read wrongly oob in MTD_OOB_PLACE.
> If I dump a page with uboot I get [1] and if I dump it with nanddump I get [2].
> As you could can see OOB doesn't match. Moreover the 2 snd 8 bytes OOB data
> given by nanddump are the 1st 8 bytes OOB of the next page.
>
> If we look in nand_base.c, we saw that in case of MTD_OOB_PLACE, the len of oob
> is set to chip->ecc.layout->oobavail. This seems wrong as user expect to be
> mtd->oobsize.
>
> Does this bug is know ?
>
Any news on that ?
I needed to patch nand_do_read_oob to use jffs2 with 2.6.20 [1].
Matthieu
[1]
if (ops->mode == MTD_OOB_RAW || ops->mode == MTD_OOB_PLACE)
len = mtd->oobsize;
else
len = chip->ecc.layout->oobavail;
prev parent reply other threads:[~2007-02-15 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 15:09 2.6.20 : BUG in nand_do_read_oob with MTD_OOB_PLACE ? Matthieu CASTET
2007-02-15 15:37 ` Matthieu CASTET [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=loom.20070215T163517-47@post.gmane.org \
--to=matthieu.castet@parrot.fr \
--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