From: Artem Bityutskiy <dedekind@infradead.org>
To: Alexey Korolev <akorolev@infradead.org>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org
Subject: Re: [PATCH] Bugfix subpage read for small page NAND.
Date: Wed, 30 Jul 2008 12:00:06 +0300 [thread overview]
Message-ID: <1217408406.9048.14.camel@sauron> (raw)
In-Reply-To: <alpine.LFD.1.10.0807291325580.23930@casper.infradead.org>
On Tue, 2008-07-29 at 13:54 +0100, Alexey Korolev wrote:
> Current implementation of subpage read feature for NAND has issues with
> small page devices. Small page NAND do not support RNDOUT command.
> So subpage feature is not applicable for them.
>
> This patch disables support of subpage for small page NAND.
> The code is verified on nandsim(SP NAND simulation) and on LP NAND
> devices.
I've put this and my nandsim fix to
git://git.infradead.org/~dedekind/mtd-fixes.git master
With those 2 patches nandsim is happy for both LP and SP NANDs.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2008-07-30 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 12:54 [PATCH] Bugfix subpage read for small page NAND Alexey Korolev
2008-07-30 9:00 ` Artem Bityutskiy [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=1217408406.9048.14.camel@sauron \
--to=dedekind@infradead.org \
--cc=akorolev@infradead.org \
--cc=dwmw2@infradead.org \
--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