From: "Stephan Linke" <Stephan.Linke@epygi.de>
To: <tglx@linutronix.de>, "Alex Samoutin" <samoutin@hotbox.ru>
Cc: Linux-Mtd <linux-mtd@lists.infradead.org>
Subject: RE: Fw: corrupt my NAND flash device
Date: Mon, 7 Jul 2003 11:27:46 +0200 [thread overview]
Message-ID: <FCEAKDJJAPHPLJFINDAJAEDGDEAA.Stephan.Linke@epygi.de> (raw)
In-Reply-To: <200307051715.14902.tglx@linutronix.de>
Hi Thomas,
>From my experience partial page write is still used by YAFFS in OOB area. And I don't know how you are doing a journaling FS on a
NAND without partial writes.
Stephan
> -----Original Message-----
> From: Thomas Gleixner [mailto:tglx@linutronix.de]
> Sent: Samstag, 5. Juli 2003 17:15
> To: Stephan Linke; Alex Samoutin
> Cc: Linux-Mtd
> Subject: Re: Fw: corrupt my NAND flash device
>
>
> On Thursday 03 July 2003 07:44, Stephan Linke wrote:
> > Hi Alex,
> >
> > I just had a look at this mail and one of the problems you mention just
> > reminds me of me experiences a few month ago. You say that write verify on
> > you NAND flash sometimes failes. I had the same on my board using YAFFS on
> > a NAND. I figured out that verify failes during partial writes. The reason
> > the compair routine doesn'T deal with that special situation where there is
> > already some data in the page and someone writes only a few 0's leaving the
> > rest at 0xFF since the manual says to do so in partial writes.
>
> We have canceled partial page writes some time ago.
>
> --
> Thomas
> ________________________________________________________________________
> linutronix - competence in embedded & realtime linux
> http://www.linutronix.de
> mail: tglx@linutronix.de
>
>
next prev parent reply other threads:[~2003-07-07 9:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 20:03 Fw: corrupt my NAND flash device Alex Samoutin
2003-04-22 20:26 ` Jörn Engel
2003-04-22 20:59 ` Jörn Engel
2003-04-23 20:45 ` Charles Manning
2003-04-24 18:25 ` Alex Samoutin
2003-04-25 13:01 ` Jörn Engel
2003-04-25 22:23 ` Alex Samoutin
2003-04-25 23:10 ` Thayne Harbaugh
2003-04-26 10:23 ` Jörn Engel
2003-04-28 15:02 ` Thayne Harbaugh
2003-04-28 21:14 ` Charles Manning
2003-04-28 22:59 ` Thomas Gleixner
2003-04-29 1:23 ` Charles Manning
2003-04-29 8:03 ` Thomas Gleixner
2003-04-29 19:37 ` Charles Manning
2003-04-29 22:04 ` Thomas Gleixner
2003-04-30 16:54 ` Alex Samoutin
2003-04-30 18:13 ` Thomas Gleixner
2003-07-02 17:43 ` Alex Samoutin
2003-07-02 17:53 ` Jasmine Strong
2003-07-02 20:10 ` Alex Samoutin
2003-07-04 1:43 ` David Woodhouse
2003-07-03 5:44 ` Stephan Linke
2003-07-05 15:15 ` Thomas Gleixner
2003-07-07 9:27 ` Stephan Linke [this message]
2003-07-07 13:48 ` Thomas Gleixner
2003-07-08 7:50 ` David Woodhouse
2003-04-26 10:18 ` Jörn Engel
2003-04-28 8:57 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 11:36 Eugeny Mints
2003-04-22 7:05 Paul Wong
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=FCEAKDJJAPHPLJFINDAJAEDGDEAA.Stephan.Linke@epygi.de \
--to=stephan.linke@epygi.de \
--cc=linux-mtd@lists.infradead.org \
--cc=samoutin@hotbox.ru \
--cc=tglx@linutronix.de \
/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