From: Sergei Shtylyov <sshtylyov@ru•mvista.com>
To: "Benedict, Michael" <MBenedict@twacs•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: MPC 8349e-mITX and MTD/Flash
Date: Tue, 10 Apr 2007 18:13:59 +0400 [thread overview]
Message-ID: <461B9BA7.1070304@ru.mvista.com> (raw)
In-Reply-To: <CF7E46FCFF66AD478BB72724345289EC2795D2@twx-exch01.twacs.local>
Hello.
Benedict, Michael wrote:
> Ben,
> I assume that you intended to CC the list but accidently hit
> "reply" instead. If not, I apologize. Thank you for all your help so
> far.
>>-----Original Message-----
>>From: Ben Warren [mailto:bwarren@qstreams•com]
>>Sent: Monday, April 09, 2007 4:30 PM
>>To: Benedict, Michael
>>Subject: Re: MPC 8349e-mITX and MTD/Flash
>>I suspect that MTD doesn't know anything about how
>>your flash chip is organized. Probably the easiest
>>thing to use is CONFIG_MTD_PHYSMAP. Using this, you
>>can either pass the MTD partitioning info via kernel
>>command line, via static physmap structures in your
>>board code or, I believe, via device tree (I haven't
>>tried the last one).
> The following is from my .config
> <snip>
> #
> # Mapping drivers for chip access
> #
> # CONFIG_MTD_COMPLEX_MAPPINGS is not set
> CONFIG_MTD_PHYSMAP=y
> CONFIG_MTD_PHYSMAP_START=0x8000000
> CONFIG_MTD_PHYSMAP_LEN=0x0
> CONFIG_MTD_PHYSMAP_BANKWIDTH=2
> # CONFIG_MTD_PHYSMAP_OF is not set
> CONFIG_MTD_PLATRAM=y
> <snip>
>
> Is this what you are referring to? Does something look obviously wrong
> with it?
Yeah, CONFIG_MTD_PHYSMAP_LEN shoudn't be 0 unless you're registering your
MTD via the platform device mechanism (and in that case specifying
CONFIG_MTD_PHYSMAP_START and CONFIG_MTD_PHYSMAP_BANKWIDTH doesn't make sense).
WBR, Sergei
next prev parent reply other threads:[~2007-04-10 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 20:58 MPC 8349e-mITX and MTD/Flash Benedict, Michael
[not found] ` <572211.38645.qm@web306.biz.mail.mud.yahoo.com>
2007-04-10 14:06 ` Benedict, Michael
2007-04-10 14:13 ` Sergei Shtylyov [this message]
2007-04-10 14:41 ` Ben Warren
2007-04-10 15:48 ` Timur Tabi
2007-04-10 16:22 ` Benedict, Michael
2007-04-10 16:48 ` Sergei Shtylyov
2007-04-10 16:48 ` Timur Tabi
2007-04-10 16:31 ` Vitaly Bordug
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=461B9BA7.1070304@ru.mvista.com \
--to=sshtylyov@ru$(echo .)mvista.com \
--cc=MBenedict@twacs$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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