From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <norris@broadcom.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: nand: nand_ids.c: added two entries for NAND chips
Date: Wed, 07 Jul 2010 17:26:34 +0300 [thread overview]
Message-ID: <1278512794.12733.27.camel@localhost> (raw)
In-Reply-To: <1276803311-6361-1-git-send-email-norris@broadcom.com>
On Thu, 2010-06-17 at 12:35 -0700, Brian Norris wrote:
> Included the basic size info for NAND chips with ID of 0xAD or
> 0xD7. The first can be found in Hynix HY27SF161G2M, while the
> second can be found in Micron MT29F64G08 and the Samsung K9LBG08U0D
> (among others). Also, some 64 Gbit (or larger) chips identify as
> 0xD7 because they contain multiple smaller 32 Gbit chips. I
> assume it's safe to classify these under the 32 Gbit listing.
I an not sure this is safe, but I guess if someone needs to support
those NANDs, they'll have to do that properly.
Pushed to l2-mtd-2.6.git / master.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-07-07 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 19:35 [PATCH] mtd: nand: nand_ids.c: added two entries for NAND chips Brian Norris
2010-07-07 14:26 ` 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=1278512794.12733.27.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=norris@broadcom.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;
as well as URLs for NNTP newsgroup(s).