From: Timur Tabi <timur@freescale.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 10:48:43 -0500 [thread overview]
Message-ID: <461BB1DB.9050503@freescale.com> (raw)
In-Reply-To: <CF7E46FCFF66AD478BB72724345289EC2795D2@twx-exch01.twacs.local>
Benedict, Michael wrote:
> # 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
This what the latest defconfig for the 8349ITX has:
CONFIG_MTD=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_CFI=y
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_UTIL=y
CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_PHYSMAP_START=0xfe000000
CONFIG_MTD_PHYSMAP_LEN=0x1000000
CONFIG_MTD_PHYSMAP_BANKWIDTH=2
Your settings for CONFIG_MTD_PHYSMAP_START and CONFIG_MTD_PHYSMAP_LEN are wrong. And
frankly, I can't understand where you got those values from, unless you created your
.config from scratch. The defconfig that's in the kernel is specifically intended for the
Freescale MPC8349E-mITX. I should know, because I wrote the code and the defconfig.
Having said that, it seems that the kernel now supports defining the physmap via the OF
tree. Is that true?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-04-10 15:48 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
2007-04-10 14:41 ` Ben Warren
2007-04-10 15:48 ` Timur Tabi [this message]
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=461BB1DB.9050503@freescale.com \
--to=timur@freescale.com \
--cc=MBenedict@twacs.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).