All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian Norris" <norris@broadcom.com>
To: "Matthieu CASTET" <matthieu.castet@parrot.com>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
	Artem Bityutskiy <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: Thu, 29 Jul 2010 16:28:25 -0700	[thread overview]
Message-ID: <4C520E99.3050006@broadcom.com> (raw)
In-Reply-To: <4C4FEC02.9050300@parrot.com>

On 07/28/2010 01:36 AM, Matthieu CASTET wrote:
> Hi,
> 
> Brian Norris a écrit :
>> I found some newer Micron parts that introduce an 8K page size, and so
>> need a modification on the algorithm. Here's the updated list and a
>> revision to my patch.
>>
> Doesn't these micron nands support onfi ?
> The micron nands we have support it.

Yes, they do support ONFI...but you missed my statements in the previous
e-mail :)

On 07/26/2010 01:04 PM, Brian Norris wrote:
> And before the question is asked: I realize that these chips support ONFI,
> so that should be the primary means by which to identify them, but I would
> still like to be able to detect these properly without ONFI if necessary,
> especially considering some of the older NAND controllers we still use do not
> support reading ONFI data.

But thanks for the interest. I guess the real question I have is: is it
possible to do a contrived detection by ID for these, even though the intent
is for detection by ONFI? If so, is my [PATCH v2] an acceptable solution?

  reply	other threads:[~2010-07-29 23:28 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 [this message]
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
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=4C520E99.3050006@broadcom.com \
    --to=norris@broadcom.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matthieu.castet@parrot.com \
    --cc=maximlevitsky@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.