From: Thomas Gleixner <tglx@linutronix.de>
To: Savin Zlobec <savin@epico.si>
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND problems with at91 kernels
Date: Mon, 19 Jun 2006 16:55:48 +0200 [thread overview]
Message-ID: <1150728949.29299.13.camel@localhost.localdomain> (raw)
In-Reply-To: <4496A162.5080305@epico.si>
On Mon, 2006-06-19 at 15:06 +0200, Savin Zlobec wrote:
> 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.
I probably missed that patch and nobody yelled loud enough. :)
I looked at the code in question and I think this is actually a problem
for FLASH chips which have the "autoincrement" feature. So after reading
one chunk, it leaves the chip in the autoread mode. Can you please check
if this still happens with the current mtd-git code ?
You need update the at91 nand code to the recent changes and when you
are at it you might resubmit the patch to MTD mailinglist so we can
include it into the official tree.
Thanks,
tglx
prev parent reply other threads:[~2006-06-19 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 13:06 NAND problems with at91 kernels Savin Zlobec
2006-06-19 14:55 ` Thomas Gleixner [this message]
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=1150728949.29299.13.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=savin@epico.si \
/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