All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huang Shijie <b32955@freescale.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org
Subject: Re: [PATCH v3 2/3] mtd: nand: add new parsing rule for Hynix's H27UBG8T2CTR
Date: Fri, 7 Mar 2014 16:00:13 +0800	[thread overview]
Message-ID: <53197C8D.3010604@freescale.com> (raw)
In-Reply-To: <20140307074657.GF31517@norris-Latitude-E6410>

于 2014年03月07日 15:46, Brian Norris 写道:
> Are you sure you need to use the device ID (0xD7)? It's best if we don't
> have to constrain ourselves to particular flash sizes here... Are there
> Hynix MLC that don't follow the id_data[5] pattern for differentiating
> technology types (>20nm vs<=20nm)? I'll have to check my datasheets
> when I get back in the office.
>
The H27UCG8T2ATR is also a 20nm chip whose device ID is 0xDE. Its 
id_data[5] is 0xc4.
But it also use the old parsing rule: the page size is the multiple of 2K.

that's why i checked the device ID.

thanks
Huang Shijie

  reply	other threads:[~2014-03-07  7:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03  8:08 [PATCH v3 0/3] mtd: nand: support more Hynix nands Huang Shijie
2014-01-03  8:08 ` [PATCH v3 1/3] mtd: nand: add a helper to parse the Hynix nand Huang Shijie
2014-03-07  7:41   ` Brian Norris
2014-03-07  7:48     ` Huang Shijie
2014-01-03  8:08 ` [PATCH v3 2/3] mtd: nand: add new parsing rule for Hynix's H27UBG8T2CTR Huang Shijie
2014-03-07  7:46   ` Brian Norris
2014-03-07  8:00     ` Huang Shijie [this message]
2014-03-07  8:08       ` Brian Norris
2014-03-07  8:15         ` Huang Shijie
2014-03-13  5:52           ` Brian Norris
2014-03-13  7:54             ` Huang Shijie
2014-01-03  8:08 ` [PATCH v3 3/3] mtd: nand: add support for H27UCG8T2B(16K + 1280) 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=53197C8D.3010604@freescale.com \
    --to=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --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 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.