From: Timo Teras <timo.teras@solidboot.com>
To: Kyungmin Park <kyungmin.park@samsung.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
Timo Teras <timo.teras@solidboot.com>
Subject: Re: OneNAND: Update OOB free table
Date: Fri, 15 Dec 2006 10:33:11 +0200 [thread overview]
Message-ID: <20061215083311.GA5793@mail.solidboot.com> (raw)
In-Reply-To: <3761211.13011166150326518.JavaMail.weblogic@ep_ml08>
On Fri, Dec 15, 2006 at 02:38:17AM +0000, Kyungmin Park wrote:
> > Tested. This breaks reading OOB area and the clean marker from there. After
> > OOB has been written without ECC it must be read without ECC too or
> >we start to get ECC errors.
>
> Yes, you're right. and the current code don't check the read error.
> It's similay problem in onenand_wait which can't report the read/write/erase error.
>
> I think I need to change the logic.
>
> First, fix the onenand_wait error report
> Second, check the read error.
>
> Anyway come back to main topic
>
> 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
>
> Is it possible?
I suppose it's worth asking from JFFS2 people. The free OOB usage seems to be
a bit broken in JFFS2 (it only uses the first pos/len pair of the OOB free
table.
Cheers,
Timo
next prev parent reply other threads:[~2006-12-15 8:34 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 [this message]
2006-12-15 10:41 ` Artem Bityutskiy
2006-12-15 11:19 ` Timo Teras
-- 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=20061215083311.GA5793@mail.solidboot.com \
--to=timo.teras@solidboot.com \
--cc=dwmw2@infradead.org \
--cc=kyungmin.park@samsung.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