public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Savin Zlobec <savin@epico.si>
To: linux-mtd@lists.infradead.org
Subject: NAND problems with at91 kernels
Date: Mon, 19 Jun 2006 15:06:42 +0200	[thread overview]
Message-ID: <4496A162.5080305@epico.si> (raw)

Hi all,

I'am running kernel 2.6.17 on AT91RM9200 board with Samsung 32MiB NAND.
I've been experiencing a lot of NAND flash errors (running JFFS2 or 
YAFFS)  which
traced down to busy delay handling. Asking on linux-arm-kernel list I've 
got a link to
this message thread:

http://lists.infradead.org/pipermail/linux-mtd/2005-September/013625.html

I've patched nand_base:nand_read_oob with the patch attached to the 
above mail and
it seems to solve my problems - I'am going to run some test for the next 
couple of days
just to be shure.

Is there any reason why this patch was not accepted and more importantly 
can I expect
more delay related problems which apperantly show only on some platforms.

Thanks,

savin

             reply	other threads:[~2006-06-19 13:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 13:06 Savin Zlobec [this message]
2006-06-19 14:55 ` NAND problems with at91 kernels 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=4496A162.5080305@epico.si \
    --to=savin@epico.si \
    --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