linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
	Guillaume LECERF <glecerf@gmail.com>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2] mtd/chips: add SST39WF160x NOR-flashes
Date: Fri, 14 May 2010 03:20:23 +0200	[thread overview]
Message-ID: <20100514012023.GA30794@pengutronix.de> (raw)
In-Reply-To: <1273797888.9999.591.camel@macbook.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

On Fri, May 14, 2010 at 01:44:48AM +0100, David Woodhouse wrote:
> On Tue, 2010-04-27 at 04:19 +0200, Wolfram Sang wrote:
> > Due to a broken CFI, they have to be added to jedec_probe.
> > 
> > Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
> > Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> > Cc: David Woodhouse <David.Woodhouse@intel.com>
> > ---
> > 
> > Sadly, those two cannot be detected using Guillaume's SST-patchset.
> 
> Why not? Guillaume has patches which add quirks for specific SST chips;
> what is fundamentally different about these chips that means you can't
> take the same approach?

See his patch 3/8. He introduces:

+#define P_ID_SST_OLD            0x0701

so, he can then do:

+       if (cfi->cfiq->P_ID == P_ID_SST_OLD) {
+               addr_unlock1 = 0x5555;
+               addr_unlock2 = 0x2AAA;
+       }
+

Only after that, he can query for more CFI-information/product ID and apply the
quirks.

My flashes don't have P_ID_SST_OLD, sadly, but P_ID_AMD_STD. Still, unlike
other AMD_STD-flashes, my flashes need their custom unlock address. I couldn't
find a way to distinguish this from the standard case with the regular unlock
addresses.

Kind regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-05-14  1:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27  2:19 [PATCH 1/2] mtd/chips: add SST39WF160x NOR-flashes Wolfram Sang
2010-04-27  2:19 ` [PATCH 2/2] mtd/chips: use common manufacturer codes in jedec_probe() Wolfram Sang
2010-04-27  6:56   ` Guillaume LECERF
2010-05-04 13:11 ` [PATCH 1/2] mtd/chips: add SST39WF160x NOR-flashes Artem Bityutskiy
2010-05-14  0:44 ` David Woodhouse
2010-05-14  1:20   ` Wolfram Sang [this message]
2010-05-14  1:28     ` David Woodhouse

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=20100514012023.GA30794@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=dwmw2@infradead.org \
    --cc=glecerf@gmail.com \
    --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 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).