Re: cmdlineparts and chip initialization order

[Thomas Gleixner <tglx@linutronix.de>]

On Thu, 2004-11-11 at 14:01 -0800, Marc Singer wrote:
> With a command line like this:
>   console=ttyAM0 root=/dev/hda1 mtdparts=norflash:2m(boot),-(root);nandflash:32k(apex)ro,-(root)
> I am able to initialization partitions for the NOR flash, but not the
> NAND flash.  It look like the problem is that the NOR flash driver is
> initializing before the mtdparts command line parsed, but the NAND
> flash isn't.
> Moving the cmdlinepart.o file to the end of the list appears to
> prevent the command line from being parsed.

The commandline parition code must be registered as a partition parser
before any mapping driver is initialized. So it's not surprising that it
does not work when it is linked in last, as the init functions are
called in link order 

> BTW, it looks like none of the other NAND drivers expect a command
> line partition setup.  Has anyone else tried?

It has nothing to do with NOR or NAND. The driver calls a parition
parser.

Provide more detailed information, please. Switch on MTD debugging and
add some MTD_DEBUG in the relevant places.

tglx