In message [off-list ref] you wrote:
i'm intrigued by the above kernel option. currently, i define my
MTD partitions in drivers/mtd/maps/rpxlite.c, using structs map_info,
mtd_info, etc., and calling the appropriate routines, which works just
fine.
will this kernel option actually let me define the basic MTD
partitions completely from the kernel command line without messing
with rpxlite.c? or am i misreading the purpose of this option?
Yes, it will.
See http://www.denx.de/twiki/bin/view/DULG/BootTimeConfigurationOfMTDPartitions
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Even if you aren't in doubt, consider the mental welfare of the per-
son who has to maintain the code after you, and who will probably put
parens in the wrong place. - Larry Wall in the perl man page
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
On Tue, 29 Jun 2004, Wolfgang Denk wrote:
In message [off-list ref] you wrote:
quoted
i'm intrigued by the above kernel option. currently, i define my
MTD partitions in drivers/mtd/maps/rpxlite.c, using structs map_info,
mtd_info, etc., and calling the appropriate routines, which works just
fine.
will this kernel option actually let me define the basic MTD
partitions completely from the kernel command line without messing
with rpxlite.c? or am i misreading the purpose of this option?
Yes, it will.
See http://www.denx.de/twiki/bin/view/DULG/BootTimeConfigurationOfMTDPartitions
excellent, this just gets better and better. however, will partition
definitions on the command line override those in rpxlite.c? i notice
that the generic rpxlite.c that comes from the bk tree has a default
partition definition of fe000000/800000. should that be removed
first? or will it be ignored? it's not clear from the comments in
the source.
rday
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
On Tue, 29 Jun 2004, Robert P. J. Day wrote:
excellent, this just gets better and better. however, will partition
definitions on the command line override those in rpxlite.c? i notice
that the generic rpxlite.c that comes from the bk tree has a default
partition definition of fe000000/800000. should that be removed
first? or will it be ignored? it's not clear from the comments in
the source.
I don't think your version of rpxlite.c supports command line
partitioning at all. The official one doesn't. You should see the
existing mapping drivers such as physmap.c to learn how to add this,
it is not difficult.
The implementation should always give precedence to the command line
defininition.
Regards,
Marius
--
Marius Groeger [off-list ref] Project Manager
SYSGO AG Embedded and Real-Time Software
Voice: +49 6136 9948 0 FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.imerva.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/