Am Donnerstag, den 10.02.2011, 17:04 +0100 schrieb Alexandre Gambier: > Dear Wolfgang, > > I tried to put some printk in the MTD driver and it seems that the > parse_mtd_partitions function is never called...
parse_mtd_partitions() is called from the mapping drivers. See e.g. linux/drivers/mtd/maps/ and linux/drivers/mtd/nand/. The mtd-id provided in kernel-cmdline has to match the name of the mapping driver, e.g. "physmap-flash" in case of drivers/mtd/maps/physmap.c. See linux/drivers/mtd/cmdlinepart.c for the format. Your spec looks fine, presumably beside "NOR" and "NAND" names. > I will try to find what's wrong with my kernel configuration. You'll need CONFIG_MTD_PARTITIONS and CONFIG_MTD_CMDLINE_PARTS. Also check /proc/cmdline that it's really passed and not overwritten by hardcoded kernel commandline (CONFIG_CMDLINE_BOOL not set). > > alex > > On 02/10/2011 03:59 PM, Wolfgang Denk wrote: > > Dear Alexandre Gambier, > > > > In message<4d53f9fa.2070...@ftemaximal.fr> you wrote: > >> mtdids : nor0=NOR,nand0=NAND > > ... > >> mtdparts=NOR:512k(U-Boot),128k(Environment),4M(Kernel),-(FreeNOR);NAND:32M(FS),-(FreeNAND) > > ... > >> The problem is that once my system is running the MTD devices in /dev > >> are not created and the file /proc/mtd is empty. > >> > >> Is my command line wrong ? > > I think so. Most probably your kernel uses different identifiers > > instead of "NOR" and "NAND". Check the kernel boot messages! > > > > Best regards, > > > > Wolfgang Denk > > > _______________________________________________ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot -- carpe noctem engineering Ingenieurbuero fuer Hard- & Software-Entwicklung Andreas Pretzsch Dipl.-Ing. (FH) Andreas Pretzsch Tel. +49-(0)731-5521572 Hahnengasse 3 Fax: +49-(0)731-5521573 89073 Ulm, Germany email: a...@cn-eng.de _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot