From: "Brian Norris" <norris@broadcom.com>
To: "Kevin Cernekee" <cernekee@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Tilman Sauerbeck <tilman@code-monkey.de>
Subject: Re: Bad assumption about ID field definition for Samsung NAND?
Date: Thu, 19 Aug 2010 15:28:13 -0700 [thread overview]
Message-ID: <4C6DAFFD.4040602@broadcom.com> (raw)
In-Reply-To: <AANLkTikiTX6US09pVu+uYm_U5=70WVbF+eH9wBtDeWKM@mail.gmail.com>
On 08/19/2010 12:46 PM, Kevin Cernekee wrote:
> The code is right; the comment is wrong.
In that case, should we fix the comment and add the
check that Tilman mentioned previously? (below)
This looks safe and will at least eliminate a few weird
cases where Samsung SLC happen to have 6-byte ID strings
(such as the K9F4G08U0B in question).
I have another fix I will tack on in series to this; should
I include you as a "Signed-off-by", Tilman?
Brian
> @@ -2852,6 +2852,7 @@ static struct nand_flash_dev *nand_get_flash_type(struct mtd_info *mtd,
> */
> if (id_data[0] == id_data[6] && id_data[1] == id_data[7] &&
> id_data[0] == NAND_MFR_SAMSUNG &&
> + (chip->cellinfo & NAND_CI_CELLTYPE_MSK) &&
> id_data[5] != 0x00) {
> /* Calc pagesize */
> mtd->writesize = 2048 << (extid & 0x03);
next prev parent reply other threads:[~2010-08-19 22:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 18:05 Bad assumption about ID field definition for Samsung NAND? Tilman Sauerbeck
2010-08-18 23:25 ` Brian Norris
2010-08-19 17:16 ` Tilman Sauerbeck
2010-08-19 19:46 ` Kevin Cernekee
2010-08-19 22:28 ` Brian Norris [this message]
2010-08-20 3:29 ` Kevin Cernekee
2010-08-20 5:38 ` Liu Hui-R64343
2010-08-20 13:43 ` Tilman Sauerbeck
2010-08-20 17:42 ` Brian Norris
2010-08-20 19:53 ` David Woodhouse
2010-08-20 20:51 ` Tilman Sauerbeck
2010-08-20 21:01 ` Brian Norris
2010-08-20 21:34 ` David Woodhouse
2010-08-20 22:05 ` Brian Norris
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=4C6DAFFD.4040602@broadcom.com \
--to=norris@broadcom.com \
--cc=cernekee@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tilman@code-monkey.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.