From: Kyungmin Park <kyungmin.park@samsung.com>
To: Timo Teras <timo.teras@solidboot.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: OneNAND: Update OOB free table
Date: Fri, 15 Dec 2006 02:38:17 +0000 (GMT) [thread overview]
Message-ID: <3761211.13011166150326518.JavaMail.weblogic@ep_ml08> (raw)
Hi, Timo
> 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?
Thank you,
Kyungmin Park
next reply other threads:[~2006-12-15 2:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 2:38 Kyungmin Park [this message]
2006-12-15 8:33 ` OneNAND: Update OOB free table Timo Teras
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=3761211.13011166150326518.JavaMail.weblogic@ep_ml08 \
--to=kyungmin.park@samsung.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=timo.teras@solidboot.com \
/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