From: Hamish Moffatt <hamish@cloud.net.au>
To: Alexey Korolev <akorolev@infradead.org>
Cc: linux-mtd@lists.infradead.org, jkimble@one.net
Subject: Re: Porting to Intel P33 flash
Date: Fri, 16 May 2008 23:18:30 +1000 [thread overview]
Message-ID: <20080516131830.GA20651@cloud.net.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0805161337350.5602@pentafluge.infradead.org>
On Fri, May 16, 2008 at 01:59:43PM +0100, Alexey Korolev wrote:
> Hi
>
> >
> > Funny you say that... I just modified the code where it checks CFI
> > version and it seems to be working without further modification. I've not
> > tested much though so I may have more to do. I do have to write to this
> > but not much.
> >
> > James
> It is good to hear this. Please check number of RWW partitons
> (numvirtchips variable) and 9th bit of extp->FeatureSupport.
> Everything is Ok if numvirtchips == 1 or extp->FeatureSupport bit 9 is 0.
>
> As I remember some versions of MTD prior to 2.6.17 had
> problems with CFI offset calculation. It led chip to be identified as
> multiple partitioned device when it should have 1 partiton.
How do you mean multiple partitions?
Here is what I see with the 8Mb P33 NOR flash with 2.6.15:
IXP4XX-Flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Intel/Sharp Extended Query Table at 0x010A
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
erase region 0: offset=0x0,size=0x20000,blocks=63
erase region 1: offset=0x7e0000,size=0x8000,blocks=4
The output with 2.6.24 is the same. I only modified 2.6.15 to recognise
the new minor revision of the P33 flash.
Anyway 2.6.15 is history for me now (we ran it for 1 year but just
upgraded to 2.6.24), I only mention it for James's information.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
prev parent reply other threads:[~2008-05-16 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 14:12 Porting to Intel P33 flash jkimble
2008-05-14 17:06 ` Alexey Korolev
2008-05-14 18:52 ` jkimble
2008-05-16 5:54 ` Hamish Moffatt
2008-05-16 12:33 ` jkimble
2008-05-16 12:59 ` Alexey Korolev
2008-05-16 13:18 ` Hamish Moffatt [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=20080516131830.GA20651@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=akorolev@infradead.org \
--cc=jkimble@one.net \
--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