All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Meade <chuckmeade@mindspring.com>
To: jkimble@one.net
Cc: linux-mtd@lists.infradead.org
Subject: Re: Strange faults using Intel P33 flash
Date: Thu, 01 May 2008 13:53:03 -0400	[thread overview]
Message-ID: <481A037F.2010106@mindspring.com> (raw)
In-Reply-To: <34025.137.237.242.42.1209662902.squirrel@webmail.nuvox.net>

jkimble@one.net wrote:
> 
> Yes it's an old 2.6.10 kernel but it's CFI NOR flash. Shouldn't it work
> with mtd circa 2.6.10?
> 
> The flash memory I am using is the Intel P33 (256P33B) NOR flash. I
> have two chips with the chip selects tied to the same logic line. The
> chips are on the Flexbus of a Coldfire processor (MCF5484). I'm able
> to work with the flash fine in the boot loader (Colilo) after porting
> the driver template from Intel into it. My question is how do I
> configure MTD to work with this. I've set the beginning address and
> the size. This is CFI complient NOR flash. I've set a chip interleave of 2
> with a 32 bit bus. As the kernel is booting I keep getting the
> message:
> 
> ================================================
> $Id: ftl.c,v 1.54 2004/11/16 18:33:15 dwmw2 Exp $
> Unlock all sector for Intel on Fire Engine...
> physmap flash device: 4000000 at f0000000
> phys_mapped_flash: Found 2 x16 devices at 0x0 in 32-bit bank
>  Intel/Sharp Extended Query Table at 0x010A
>   Unknown Intel/Sharp Extended Query version 1.4.

I ran into something similar on a 2.6.11 variant.  The MTD of that era does
not support the version of CFI Extended Query found in the P33 flash.
What you can do is either a) use a newer kernel version which does support
this Extended Query version, or b) backport the bits of MTD logic that support
this Extended Query version from a newer kernel to your kernel.

If it is possible (for numerous reasons) it is preferable to use a newer
kernel version that has built-in support for the Extended Query version in
the P33 flash.

HTH,
Chuck

      reply	other threads:[~2008-05-01 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01 17:28 Strange faults using Intel P33 flash jkimble
2008-05-01 17:53 ` Chuck Meade [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=481A037F.2010106@mindspring.com \
    --to=chuckmeade@mindspring.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.