[Help] SST39VF6401B Support
Flávio Silveira
fggs at terra.com.br
Thu Sep 23 08:34:12 EDT 2010
Hi Guillaume,
I know you asked for Wolfram logs but just for you to know, I tried
enabling DEBUG_CFI but no new output than before.
Never tried DEBUG_CFI_FEATURES though.
What output should I expect from both? The only thing I see is "pflash:
cfi_probe failed"
Regards,
Flavio
----- Original Message -----
From: "Guillaume LECERF" <glecerf at gmail.com>
To: "Wolfram Sang" <w.sang at pengutronix.de>
Cc: "Flávio Silveira" <fggs at terra.com.br>; <linux-mtd at lists.infradead.org>;
"Yegor Yefremov" <yegorslists at googlemail.com>
Sent: Thursday, September 23, 2010 9:23 AM
Subject: Re: [Help] SST39VF6401B Support
2010/9/23 Wolfram Sang <w.sang at pengutronix.de>:
>
>> Thanks for your response. Does this mean this chip isn't CFI
>> compliant? Like, datasheet says it is, but not really.
>
> SST? Broken CFI happened to me, too :(
> http://patchwork.ozlabs.org/patch/51027/
This patch [1] (tried to) add support for your chip.
According to the datasheet [2], it uses addr_unlock1 = 0x555 and
addr_unlock2 = 0x2AA, and has no extended query table.
So this chip must be handled by the fixup_sst39vf_rev_b() fixup function.
Could you provide us with a more detailed log, i.e. with
DEBUG_CFI_FEATURES enabled in cfi_cmdset_0002.c and DEBUG_CFI in
cfi_probe.c ?
[1] http://patchwork.ozlabs.org/patch/50906/
[2] http://www.sst.com/dotAsset/40661.pdf
--
Guillaume LECERF
GeeXboX developer - www.geexbox.org
More information about the linux-mtd
mailing list