What is the naming scheme of MTD partitions listed in the following boot log?
5 cmdlinepart partitions found on MTD device phys_mapped_flash Creating 5 MTD partitions on "phys_mapped_flash": 0x00000000-0x00080000 : "bootloader" 0x00080000-0x00680000 : "kernel" 0x00680000-0x01680000 : "rootfs" 0x01680000-0x01780000 : "data" 0x01780000-0x017a0000 : "bootload-env"
In particular, I am asking what naming scheme to use to specify the "rootfs" partition in the U-Boot prompt as an argument to the command:
setenv bootargs 'root= ???????'
IMO, I need to specify the root= because the boot log shows, that the kernel does not know what the root device is.
VFS: Cannot open root device "<NULL>" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
...and also the boot log shows:
Kernel command line: bootoctlinux 0x2a00200 mtdparts=phys_mapped_flash:512k(bootloader)ro,6M(kernel),16M(rootfs),1024k(data),128k(bootload-env) console=ttyS0,115200
BTW: The root file system is stored in an embedded section (.init.ramfs) of the kernel ELF file (vmlinux64) as a gzipped cpio archive and the boot log indicates, that it is loaded into RAM successfully:
Loading .init.ramfs @ 0xffffffff806ac000 (0x185ac7 bytes)
This is on an embedded system with 32MB of flash storage only ( Linux kernel v126.96.36.199 ( Distro: Cavium-Octeon for MIPS64 ) ).
U-Boot 1.1.1 (Development build, svnversion: 176)
Some people say it is MTD1, some that MTD2 some /dev/MTD1, some /dev/mtd1, some that it is MTDblock1, some mtdblock1, some mtdblock2, some ubi.mtdblock1, some ubi:mtdblock1, (why the colon?) etc....
What is the truth? How can it be discovered from only the U-Boot prompt or the boot log?