adding cmd-line partitioning to rpxlite.c
Robert P. J. Day
rpjday at mindspring.com
Fri Jul 2 08:26:23 EDT 2004
i was going to take a shot at adding command-line partitioning to
rpxlite.c (seems easy enough), but was confused by an example shown in
another map file.
according to cmdlinepart.c, the format for the command line is:
* mtdparts=<mtddef>[;<mtddef]
* <mtddef> := <mtd-id>:<partdef>[,<partdef>]
* <partdef> := <size>[@offset][<name>][ro]
* <mtd-id> := unique name used in mapping driver/device (mtd->name)
* <size> := standard linux memsize OR "-" to denote all remaining space
* <name> := '(' NAME ')'
from what i've seen, each partition has to have an <mtddef> identifier
to associate to a map. i thought that this identifier corresponded to
the map_info.name field (that would make sense), but in
lubbock_flash.c, i notice the definitions in defining maps for two
flash chips:
lubbock_maps[flashboot^1].name = "Lubbock Application Flash";
lubbock_maps[flashboot].name = "Lubbock Boot ROM";
these name values have embedded spaces. how exactly does that work in
trying to use command-line partitioning here? or did i misread how to
specify the <mtddef> field on the the command line?
or, to be more brief, how would one use command-line partitioning for
lubbock-flash.c? i'm going to do a more careful re-reading of
cmdlinepart.c to see what i missed. thanks.
rday
More information about the linux-mtd
mailing list