From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <norris@broadcom.com>
Subject: Re: [PATCH v2] mtd/nand: Support Micron chips, pagesize >= 4KB
Date: Mon, 23 Aug 2010 10:22:05 +0200 [thread overview]
Message-ID: <4C722FAD.2030501@parrot.com> (raw)
In-Reply-To: <AANLkTim-XofxxyZt6epCcoQN=PL0vFdT0vjmk_5D=soY@mail.gmail.com>
hi,
Kevin Cernekee a écrit :
> On Sun, Aug 22, 2010 at 1:20 AM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
>> I'm not picking this patch to my l2-mtd-2.6.git, since AFAICS the chips
>> support ONFI should be detected properly.
>>
>> The "older chips" which do not support reading ONFI data can then be
>> detected using special quirks. But using heuristics even for the chips
>> which do support reading ONFI data sounds bad.
>
> The NAND controllers on certain legacy SoCs are not able to read the
> ONFI parameter page, even if the flash device itself supports ONFI.
Why ?
Are there controllers that doesn't allow to send custom command ?
Matthieu
next prev parent reply other threads:[~2010-08-23 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 20:04 [PATCH] mtd/nand: Support Micron chips, 4KB page Brian Norris
2010-07-27 19:42 ` [PATCH v2] mtd/nand: Support Micron chips, pagesize >= 4KB Brian Norris
2010-07-28 8:36 ` Matthieu CASTET
2010-07-29 23:28 ` Brian Norris
2010-08-22 8:14 ` Artem Bityutskiy
2010-08-22 8:20 ` Artem Bityutskiy
2010-08-22 22:20 ` Kevin Cernekee
2010-08-23 8:22 ` Matthieu CASTET [this message]
2010-08-23 21:48 ` Kevin Cernekee
2010-08-24 6:10 ` Artem Bityutskiy
2010-08-26 0:43 ` Kevin Cernekee
2010-08-30 12:32 ` Artem Bityutskiy
2010-08-05 4:31 ` [PATCH] mtd/nand: Support Micron chips, 4KB page Artem Bityutskiy
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=4C722FAD.2030501@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=cernekee@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=maximlevitsky@gmail.com \
--cc=norris@broadcom.com \
--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;
as well as URLs for NNTP newsgroup(s).