From: Scott Wood <scottwood@freescale.com>
To: Ron Madrid <ron_madrid@sbcglobal.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: JFFS2 FS not writeable
Date: Tue, 27 May 2008 16:03:22 -0500 [thread overview]
Message-ID: <483C771A.7050003@freescale.com> (raw)
In-Reply-To: <850932.26140.qm@web83511.mail.sp1.yahoo.com>
Ron Madrid wrote:
> In which function should I start searching for this
> problem? What would cause a block to be marked bad?
No particular function; just something that causes things to not work. :-P
You may want to try increasing the OR[SCY] field or other timing
parameters associated with the NAND flash.
-Scott
next prev parent reply other threads:[~2008-05-27 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 20:36 JFFS2 FS not writeable Ron Madrid
2008-05-22 21:15 ` Sean MacLennan
2008-05-22 21:16 ` Scott Wood
2008-05-27 18:03 ` Ron Madrid
2008-05-27 18:07 ` Scott Wood
2008-05-27 20:26 ` Ron Madrid
2008-05-27 21:03 ` Scott Wood [this message]
2008-05-28 18:39 ` Ron Madrid
2008-05-28 18:42 ` Scott Wood
2008-05-29 0:32 ` Ron Madrid
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=483C771A.7050003@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ron_madrid@sbcglobal.net \
/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;
as well as URLs for NNTP newsgroup(s).