From: Pieter <phenning@vastech.co.za>
To: linuxppc-dev@ozlabs.org
Subject: Need help with kernel config to set MTD partitions
Date: Wed, 11 Feb 2009 15:04:15 +0200 [thread overview]
Message-ID: <4992CCCF.1020008@vastech.co.za> (raw)
[-- Attachment #1: Type: text/plain, Size: 2017 bytes --]
Hi all
Im Trying to boot a MPC8548 board using CRAMFS ( I am able to boot a
network file system). Im using the powerpc architecture and flattened
device tree containing my flash partitions. the previous linux i booted
using CRAMFS used mtd/map definition for my board. do i still need to
define a mdt map if I'm using a flattened device tree?
How do i configure the kernal to use CFI and configure teh MTD
partitions i have? do i use
CONFIG_MTD_PHYSMAP or CONFIG_MTD_PHYSMAP_OF.
as far as i understand to use the mtd/maps I would use
CONFIG_MTD_COMPLEX_MAPPINGS.
Are the config settings for the FTD and mtd/maps mutually exclusive?
my current config regarding CFI and MTD looks as follows"
CONFIG_MTD=y
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=3
CONFIG_MTD_CONCAT=y
CONFIG_MTD_PARTITIONS=y
# CONFIG_MTD_REDBOOT_PARTS is not set
##CONFIG_MTD_OF_PARTS=m
# CONFIG_MTD_AR7_PARTS is not set
CONFIG_MTD_CMDLINE_PARTS=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_BLOCK_RO=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
CONFIG_MTD_OOPS=m
-
# RAM/ROM/Flash chip drivers
#
CONFIG_MTD_CFI=y
#CONFIG_MTD_JEDECPROBE=m
CONFIG_MTD_GEN_PROBE=y
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
#CONFIG_MTD_MAP_BANK_WIDTH_1=y
#CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
# CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
#CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_CFI_I4 is not set
# CONFIG_MTD_CFI_I8 is not set
# CONFIG_MTD_CFI_INTELEXT is not set
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_AMDSTD_RETRY=0
#CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=y
#CONFIG_MTD_RAM=m
CONFIG_MTD_ROM=y
##CONFIG_MTD_ABSENT=m
Mapping drivers for chip access
#
#CONFIG_MTD_COMPLEX_MAPPINGS=y
#CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_PHYSMAP_OF=y
# CONFIG_MTD_PCI is not set
# CONFIG_MTD_INTEL_VR_NOR is not set
#CONFIG_MTD_PLATRAM=m
thanks pieter
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2722 bytes --]
reply other threads:[~2009-02-11 13:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4992CCCF.1020008@vastech.co.za \
--to=phenning@vastech.co.za \
--cc=linuxppc-dev@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).