Command line partition support in 2.6

Command line partition support in 2.6

[Robin Gilks]

Greetings

I'm just moving from a 2.4 to 2.6 kernel and am trying to make sense of 
the command line partition support. In 2.4 I added a definition in 
maps/physmap.c


struct map_info physmap_map = {
	.name = "asif",
	.size = CONFIG_MTD_PHYSMAP_LEN,
	.buswidth = CONFIG_MTD_PHYSMAP_BUSWIDTH,
	.phys = CONFIG_MTD_PHYSMAP_START,
};

and used a kernel command line of the form:
      mtdparts=asif:64K(param),3008K(jffs),256K(u-boot),-(kernel)

to partition the flash.

What is the equivalent procedure now? All the documentation seems to 
skim over NOR straight into NAND and all the example maps I've looked at 
use a fixed partition map rather than a command line one.

I'm sure its really simple but it beats me at the moment!!

Cheers

-- 
Robin


=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================

Re: Command line partition support in 2.6

[Robin Gilks]

Robin Gilks wrote:
> Greetings
> 
> I'm just moving from a 2.4 to 2.6 kernel and am trying to make sense of 
> the command line partition support. In 2.4 I added a definition in 
> maps/physmap.c
> 
> 
> struct map_info physmap_map = {
> 	.name = "asif",
> 	.size = CONFIG_MTD_PHYSMAP_LEN,
> 	.buswidth = CONFIG_MTD_PHYSMAP_BUSWIDTH,
> 	.phys = CONFIG_MTD_PHYSMAP_START,
> };
> 
> and used a kernel command line of the form:
>       mtdparts=asif:64K(param),3008K(jffs),256K(u-boot),-(kernel)
> 
> to partition the flash.
> 
> What is the equivalent procedure now? All the documentation seems to 
> skim over NOR straight into NAND and all the example maps I've looked at 
> use a fixed partition map rather than a command line one.
> 
> I'm sure its really simple but it beats me at the moment!!
> 
> Cheers
> 

Took me a day but at last I found the '.0' that was being stuck on the 
end of the physmap-flash string as the mtd-id. Duh.

Is there a way of creating an id without the '.<num>' extention so I can 
keep some bootloader compatability twixt 2.4 & 2.6 kernels?

-- 
Robin


=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================