From: Timo Teras <timo.teras@solidboot.com>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Timo Teras <timo.teras@solidboot.com>
Subject: Re: OneNAND: Update OOB free table
Date: Fri, 15 Dec 2006 13:19:00 +0200 [thread overview]
Message-ID: <20061215111900.GB5793@mail.solidboot.com> (raw)
In-Reply-To: <1166179313.18628.52.camel@sauron>
On Fri, Dec 15, 2006 at 12:41:53PM +0200, Artem Bityutskiy wrote:
> On Fri, 2006-12-15 at 02:38 +0000, Kyungmin Park wrote:
> > How about the the change the JFFS2 logic to skip the eccpos in cleanmark check.
> > In onenand_oob_64, it describes the eccpos. So the JFFS2 skip the eccpos
>
> May you refine what is the problem please?
jffs2_check_oob_empty() check that the whole OOB area contains only 0xff
bytes except for the clean marker area. This is broken on OneNAND as writing
clean marker to OOB area will change ECC bytes.
Also the clean marker is not written properly as only the first oobfree
table element is used. But this is a different issue.
- Timo
next prev parent reply other threads:[~2006-12-15 11:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 2:38 OneNAND: Update OOB free table Kyungmin Park
2006-12-15 8:33 ` Timo Teras
2006-12-15 10:41 ` Artem Bityutskiy
2006-12-15 11:19 ` Timo Teras [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-26 7:15 Kyungmin Park
2006-12-22 1:52 Kyungmin Park
2006-12-22 9:17 ` Artem Bityutskiy
2006-12-18 4:24 Kyungmin Park
2006-12-18 14:23 ` Artem Bityutskiy
2006-12-21 11:15 ` Artem Bityutskiy
2006-12-21 12:35 ` Artem Bityutskiy
2006-12-08 0:11 Kyungmin Park
2006-12-08 8:43 ` Timo Teras
2006-12-11 12:20 ` Timo Teras
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=20061215111900.GB5793@mail.solidboot.com \
--to=timo.teras@solidboot.com \
--cc=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--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