public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Huang Shijie <b32955@freescale.com>
Cc: Graham Moore <ggrahammoore@gmail.com>,
	Geert Uytterhoeven <geert+renesas@linux-m68k.org>,
	Insop Song <insop.song@gainspeed.com>,
	Graham Moore <grmoore@altera.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Jingoo Han <jg1.han@samsung.com>,
	linux-kernel@vger.kernel.org,
	Yves Vandervennet <rocket.yvanderv@gmail.com>,
	linux-mtd@lists.infradead.org,
	Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
	Alan Tull <atull@altera.com>,
	Sourav Poddar <sourav.poddar@ti.com>,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	Dinh Nguyen <dinguyen@altera.com>
Subject: Re: [PATCH V3] Add support for flag status register on Micron chips.
Date: Fri, 25 Apr 2014 17:50:54 +0200	[thread overview]
Message-ID: <201404251750.54582.marex@denx.de> (raw)
In-Reply-To: <20140425044703.GD24530@localhost>

On Friday, April 25, 2014 at 06:47:04 AM, Huang Shijie wrote:
> On Tue, Apr 22, 2014 at 01:48:21PM -0500, Graham Moore wrote:
> > On Tue, Apr 22, 2014 at 11:55 AM, Marek Vasut <marex@denx.de> wrote:
> > > Are you sure the n25q512a doesn't use FSR ? Do n25q512a{1,8}3 share the
> > > same IDs?
> > 
> > I looked at the datasheet and the n25q512a *does* have the same FSR
> > usage note, so I suppose I should add USE_FSR to it as well.  But how
> > is it working now?  Maybe nobody is actually using that chip.
> > Yes, n25q512a{1,8}3 share the same id, 0x20ba20.
> 
> could use the ext_id to distinguish them ? just as we did for Spansion NOR.
> 
> i dumped out 5 bytes of my n25q256a: 0x20, 0xba, 0x19, 0x10, 0x00.

The q256 and q512 are rather different chips it seems to me ...

Best regards,
Marek Vasut

  reply	other threads:[~2014-04-25 16:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 14:03 [PATCH V3] Add support for flag status register on Micron chips Graham Moore
2014-04-22 14:03 ` Graham Moore
2014-04-22 16:55   ` Marek Vasut
2014-04-22 18:48     ` Graham Moore
2014-04-22 18:58       ` Marek Vasut
2014-04-25  4:47       ` Huang Shijie
2014-04-25 15:50         ` Marek Vasut [this message]
2014-04-22 18:45   ` Gerhard Sittig
2014-04-22 19:17     ` Graham Moore
2014-04-25  1:34   ` Huang Shijie
2014-04-25  2:42     ` Marek Vasut
2014-04-25  1:52       ` Huang Shijie
2014-04-25 22:12         ` Marek Vasut
2014-04-26  3:10           ` Huang Shijie
2014-04-28  5:06             ` Marek Vasut
2014-04-28  7:06               ` Huang Shijie
2014-04-28 14:22                 ` Graham Moore
2014-04-28 15:37                   ` Huang Shijie
2014-07-12  2:07               ` Brian Norris
2014-04-25  1:54       ` Huang Shijie

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=201404251750.54582.marex@denx.de \
    --to=marex@denx.de \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=atull@altera.com \
    --cc=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=dinguyen@altera.com \
    --cc=dwmw2@infradead.org \
    --cc=geert+renesas@linux-m68k.org \
    --cc=ggrahammoore@gmail.com \
    --cc=grmoore@altera.com \
    --cc=insop.song@gainspeed.com \
    --cc=jg1.han@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rocket.yvanderv@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sourav.poddar@ti.com \
    /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