From: Thomas Gleixner <tglx@linutronix.de>
To: "Edward J. Lee" <noshel@idis.co.kr>, linux-mtd@lists.infradead.org
Subject: Re: A question on ECC
Date: Fri, 18 Apr 2003 10:49:02 +0200 [thread overview]
Message-ID: <200304181049.02754.tglx@linutronix.de> (raw)
In-Reply-To: <3E9FC99D.5040200@idis.co.kr>
On Friday 18 April 2003 11:47, Edward J. Lee wrote:
>
> I tried this last night, and I got a bunch of "YAFFS ReadChunk with real
> ECC_INFO".
> when both reading/writing.
> Nothing else, do we need more information?
I assume there were no messages containing YAFFS ReadChunk with dummy ECC
info.
That means, YAFFS supplies always a pointer to yaffs_oobinfo structure.
Do the "I'ts not recommended ...." messages follow up the above message, or
show they up elsewhere ? That means, are they really related to accessing the
YAFFS partitions ? Please provide a short debug output, where I can see the
context of those "It's not recommended ..." messages.
Are there any other functions accessing the flash device ?
You use 2 partitions out of 5 for YAFFS. What are the other partitions for?
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2003-04-18 7:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 0:18 A question on ECC Edward Lee \(이장원\)
2003-04-14 2:01 ` Earl Manning
2003-04-14 5:13 ` Edward Lee (???)
2003-04-14 7:54 ` Thomas Gleixner
2003-04-14 17:40 ` Edward J. Lee
2003-04-14 10:03 ` Gerhard Uttenthaler
2003-04-14 11:17 ` Thomas Gleixner
2003-04-14 11:25 ` Thomas Gleixner
2003-04-18 9:47 ` Edward J. Lee
2003-04-18 8:49 ` Thomas Gleixner [this message]
2003-04-19 4:14 ` Edward Lee (???)
2003-04-19 7:31 ` Thomas Gleixner
2003-04-14 14:06 ` Earl Manning
2003-04-14 15:26 ` Thomas Gleixner
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=200304181049.02754.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=noshel@idis.co.kr \
/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