From: Peter Turczak <peter@turczak.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH for 3.7] mtd: nand: fix Samsung SLC NAND identification regression
Date: Mon, 12 Nov 2012 12:53:44 +0000 (UTC) [thread overview]
Message-ID: <loom.20121112T134210-779@post.gmane.org> (raw)
In-Reply-To: <1349850366-4731-1-git-send-email-computersforpeace@gmail.com>
Hi Brian,
> This patch re-introduces a distinction between these old and new Samsung
> NAND by checking that the 6th byte is non-zero, allowing both old and
> new Samsung NAND to be detected properly.
Currently we're observing the same problem with our Samsung K9F2G08U0D nand
device, but the patch provided does not resolve the issue.
Ours read back {0xec, 0xdc, 0x10, 0x95, 0x54, 0xec, 0xec, 0xdc}. The Samsung
datasheet
seems to be consistent with the routine called when neither Samsung or Hynix
6 byte IDs are detected.
>From your patch I deduce, maybe one could also check for 0xEC at the 6th byte
in order to find an old ID format?
Or maybe it might help to analyze the 2nd byte, as it is intended to be a
evice code.
( 0xDC for K9F4G08U0D,
0xD3 for K9K8G08U0D,
0xDC for K9K8G08U1D
and 0xD3 for K9WAG08U1D)
Anyway, it leads to a more convoluted code...
I would be very grateful to be hearing from you in this regard.
Best regards,
Peter
prev parent reply other threads:[~2012-11-12 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 6:26 Brian Norris
2012-10-10 6:31 ` David Woodhouse
2012-10-10 6:39 ` Brian Norris
2012-10-10 7:48 ` David Woodhouse
2012-10-10 10:35 ` Marek Vasut
2012-10-31 16:20 ` Brian Norris
2012-10-31 16:45 ` Marek Vasut
2012-11-12 12:53 ` Peter Turczak [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=loom.20121112T134210-779@post.gmane.org \
--to=peter@turczak.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome