From: "Flávio Silveira" <fggs@terra.com.br>
To: "Yegor Yefremov" <yegorslists@googlemail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [Help] SST39VF6401B Support
Date: Thu, 23 Sep 2010 11:56:38 -0300 [thread overview]
Message-ID: <6E1A182A06054C5A99BD3C0D3202C24F@THOR> (raw)
In-Reply-To: <AANLkTikXbKZLFOCBDkrwgVPJEYTwF88xBtYFnwaTQH+5@mail.gmail.com>
Hi Yegor,
I think I might found something:
In cfi_probe.c, starting at line 222, there are these lines:
cfi_send_gen_cmd(0xaa, addr_unlock1, base, map, cfi, cfi->device_type,
NULL);
cfi_send_gen_cmd(0x55, addr_unlock2, base, map, cfi, cfi->device_type,
NULL);
cfi_send_gen_cmd(0x90, addr_unlock1, base, map, cfi, cfi->device_type,
NULL);
Which seems the correct way to CFI query the chip, but the last line is
0x90.
Datasheet states that 0x90 is Software ID and CFI Query Entry is 0x98
Could that be the problem?
Regards,
Flavio
----- Original Message -----
From: "Yegor Yefremov" <yegorslists@googlemail.com>
To: "Flávio Silveira" <fggs@terra.com.br>
Cc: <linux-mtd@lists.infradead.org>
Sent: Thursday, September 23, 2010 10:45 AM
Subject: Re: [Help] SST39VF6401B Support
>> It's kernel 2.6.23 with some patches, they call it 2.6.24.111
>
> It is really old! This is a gap of more than 10 kernel versions! Any
> chance to get something newer? 2.6.35?
>
> I could imagine, that the patches mentioned in this thread could fail
> due to old kernel. Many things like JEDEC and CFI probes were greatly
> improved since then. I tested my patch for 2.6.29. .27 and .28 may
> also work.
>
> Yegor
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2010-09-23 14:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 3:43 [Help] SST39VF6401B Support Flávio Silveira
2010-09-23 7:28 ` Yegor Yefremov
2010-09-23 11:01 ` Flávio Silveira
2010-09-23 12:05 ` Wolfram Sang
2010-09-23 12:15 ` Flávio Silveira
2010-09-23 12:37 ` Wolfram Sang
2010-09-23 12:23 ` Guillaume LECERF
2010-09-23 12:34 ` Flávio Silveira
2010-09-23 15:21 ` Fabio Giovagnini
2010-09-23 12:18 ` Yegor Yefremov
2010-09-23 12:30 ` Flávio Silveira
2010-09-23 12:33 ` Yegor Yefremov
2010-09-23 12:40 ` Flávio Silveira
2010-09-23 13:45 ` Yegor Yefremov
2010-09-23 13:56 ` Flávio Silveira
2010-09-23 14:56 ` Flávio Silveira [this message]
2010-09-23 15:14 ` Yegor Yefremov
2010-09-23 15:33 ` Guillaume LECERF
2010-09-24 10:56 ` Flávio Silveira
2010-10-05 9:38 ` Guillaume LECERF
2010-10-05 10:07 ` Flávio Silveira
2010-10-05 10:12 ` Guillaume LECERF
2010-10-12 10:48 ` Guillaume LECERF
2010-10-17 20:22 ` Flávio Silveira
-- strict thread matches above, loose matches on Subject: below --
2010-10-16 7:08 Re :Re: " yidong zhang
2010-10-22 15:36 ` Guillaume LECERF
2010-10-22 15:42 ` yidong zhang
2010-10-22 17:50 ` Fabio Giovagnini
2011-06-16 0:55 ` Flávio Silveira
2011-06-20 3:12 ` Flávio Silveira
2011-06-20 3:36 ` yidong zhang
2011-06-20 23:55 ` Flávio Silveira
2011-12-08 21:21 ` Flávio Silveira
2011-12-09 23:15 ` Flávio Silveira
2011-12-10 0:54 ` Guillaume LECERF
2011-12-10 1:56 ` Flávio Silveira
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=6E1A182A06054C5A99BD3C0D3202C24F@THOR \
--to=fggs@terra.com.br \
--cc=linux-mtd@lists.infradead.org \
--cc=yegorslists@googlemail.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