From: Brian Szmyd <brian.szmyd@quantum.com>
To: linux-mtd@lists.infradead.org
Subject: Partitioning NAND flash
Date: Thu, 04 Sep 2008 12:49:22 -0600 [thread overview]
Message-ID: <1220554162.4879.64.camel@lethargic> (raw)
I am having trouble determining where the partitioning information is
coming from when I boot into linux 2.6.26 for my haleakala reference
board from amcc. When linux boots I receive the following output from
the MTD driver:
fc000000.nor_flash: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
fc000000.nor_flash: CFI does not contain boot bank location. Assuming
top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
Creating 5 MTD partitions on "fc000000.nor_flash":
0x00000000-0x001e0000 : "kernel"
0x001e0000-0x00200000 : "dtb"
0x00200000-0x00f60000 : "root"
0x03f60000-0x03fa0000 : "env"
0x03fa0000-0x04000000 : "u-boot"
NDFC NAND Driver initialized. Chip-Rev: 0x00000111
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB
3,3V 8-bit)
Scanning device for bad blocks
Number of partitions 3
Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x00000000-0x00060000 : "u-boot"
0x00060000-0x00068000 : "env"
0x00068000-0x04000000 : "content"
My problem is that I want to repartition the NAND flash, but am not sure
where the current partitioning scheme is coming from. My bootargs to the
kernel does not contain an mtdparts section and i don't see any
reference to a "u-boot", "env", "content" partition in the mtd driver
code itself.
I have setup my NOR partitioning by modifying the DTS provided by the
linux source, but there is nothing in there that refers to the NAND
chip. I have tried providing an mtdparts argument to the kernel but this
appears to be a no-op even though the appropriate option in the kernel
is configured.
I'm kind of at a loss after monkeying with this for the last couple
days. Any help or direction to a good source of information would be
greatly appreciated!
Brian Szmyd | brian.szmyd@quantum.com
-----------------------------------------------------------
The information contained in this transmission may be
confidential. Any disclosure, copying, or further
distribution of confidential information is not permitted
unless such privilege is explicitly granted in writing by
Quantum Corporation. Furthermore, Quantum Corporation is not
responsible for the proper and complete transmission of the
substance of this communication or for any delay in its
receipt.
------------------------------------------------------------
next reply other threads:[~2008-09-04 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 18:49 Brian Szmyd [this message]
2008-09-05 5:06 ` Partitioning NAND flash Eirik Aanonsen
2008-09-05 14:38 ` Brian Szmyd
2008-09-05 7:17 ` Hinko Kocevar
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=1220554162.4879.64.camel@lethargic \
--to=brian.szmyd@quantum.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox