Re: cmdlineparts and chip initialization order

[Marc Singer <elf@buici.com>]

On Thu, Nov 11, 2004 at 11:51:13PM +0100, Thomas Gleixner wrote:
> Provide more detailed information, please. Switch on MTD debugging and
> add some MTD_DEBUG in the relevant places.

In this dmesg dump, you can see that the CMDLINE-PART stuff occurs
before the NAND driver is initialized and after the NOR driver.  I am
assuming that this is the reason that the nand driver doesn't receive
partitions.  Is this not the case?


lpd79524 flash device: 1000000 at 44000000
lpd79524_norflash: Found 1 x16 devices at 0x0 in 16-bit bank
lpd79524_norflash: Found 1 x16 devices at 0x800000 in 16-bit bank
 Intel/Sharp Extended Query Table at 0x0031
cfi_cmdset_0001: Erase suspend on write enabled
Using buffer write method
DEBUG-CMDLINE-PART: parse_cmdline_partitions top
DEBUG-CMDLINE-PART: parsing <2m(boot),-(root);lpd79524_nandflash:32k(apex)ro,-(>
DEBUG-CMDLINE-PART: partition 1: name <root>, offset 0, size ffffffff, mask fla0
DEBUG-CMDLINE-PART: partition 0: name <boot>, offset 0, size 200000, mask flags0
DEBUG-CMDLINE-PART: mtdid=<lpd79524_norflash> num_parts=<2>
DEBUG-CMDLINE-PART: parsing <32k(apex)ro,-(root)>
DEBUG-CMDLINE-PART: partition 1: name <root>, offset 0, size ffffffff, mask fla0
DEBUG-CMDLINE-PART: partition 0: name <apex>, offset 0, size 8000, mask flags 3
DEBUG-CMDLINE-PART: mtdid=<lpd79524_nandflash> num_parts=<2>
2 cmdlinepart partitions found on MTD device lpd79524_norflash
Creating 2 MTD partitions on "lpd79524_norflash":
0x00000000-0x00200000 : "boot"
mtd: Giving out device 0 to boot
0x00200000-0x01000000 : "root"
mtd: Giving out device 1 to root
NAND device: Manufacturer ID: 0x98, Chip ID: 0x75 (Toshiba NAND 32MiB 3,3V 8-bi)
Scanning device for bad blocks
mtd: Giving out device 2 to lpd79524_nandflash