From: Jeff Sutherland <jeffs@fomsystems.com>
To: Vernon Sauder <vernoninhand@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd concatenate support for pxa2xx-flash mapping driver
Date: Fri, 5 Sep 2008 18:59:02 -0400 [thread overview]
Message-ID: <200809051859.03206.jeffs@fomsystems.com> (raw)
In-Reply-To: <48C0B79E.2020909@gmail.com>
On Friday 05 September 2008, apparently Vernon Sauder wrote:
> Jeff Sutherland wrote:
> > I'm working currently in 2.6.25. Is anyone working on mtd concatenation
> > support for this particular driver? $customer selected 64Mbyte NOR flash
> > chip for root filesystem, but in reality it is two 32Mb die in one
> > package, and I need one mtd partition > 32mb after taking care of
> > bootloader, environment, and kernel.
>
> Is this the P30 strataflash 48F4400 variety? I created a custom patch
> for that but converted to using the phymap-flash support from 2.6.25.1
> and backported it to 2.6.24.4. I use the command line parsing.
I got this sorted out today. It turns out the physmap-flash driver will fail
silently if you specify a command line partition that spans twom chips. In
other words, I had specified in the kernel config the total size of installed
flash, but had left unchecked config_mtd_concat. On startup physmap-flash
would correctly identify both chips inside the 48F4400 part, and even let me
make a partition (passed in from the kernel command line) that spanned the
boundary between chips. But jffs2 had a cow with the smaller erase blocks at
the 32m boundary. Simply turning on CONFIG_MTD_CONCAT solved all the
problems, sigh...
Regards,
-Jeff
prev parent reply other threads:[~2008-09-05 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 17:59 mtd concatenate support for pxa2xx-flash mapping driver Jeff Sutherland
[not found] ` <48C0B79E.2020909@gmail.com>
2008-09-05 22:59 ` Jeff Sutherland [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=200809051859.03206.jeffs@fomsystems.com \
--to=jeffs@fomsystems.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vernoninhand@gmail.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