Thanks all for your help.
Now, the system is able to create a partition for ROMfs.
So it seems that the kernel has found -rom1fs- thanks to uClinux.c.
ROOT_DEV has been set at 1f:00 (31, 0).
But I have still a kernel panic.
Perhaps I have missed something.
Any suggestions?
Thanks in advance.
S.Lambert
*************************************************************************
Linux version 2.6.19-uc1 (gcc version 4.1.2 20080812 (Cortus release))
#353 Wed Jan 14 11:43:24 CET 2009
romfs start : 70620
Built 1 zonelists. Total pages: 1992
Kernel command line:
PID hash table entries: 32 (order: 5, 128 bytes)
Dentry cache hash table entries: 1024 (order: 0, 4096 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mem_init: start=313dc, end=7d7420
Memory available: 1958k/7744k RAM, (597k kernel code, 67k data)
Mount-cache hash table entries: 512
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
uclinux[mtd]: RAM probe address=0x11414 size=0x1000
Creating 1 MTD partitions on "RAM":
0x00000000-0x00001000 : "ROMfs"
uclinux[mtd]: set ROMfs to be root filesystem
*******
VFS: test name = </dev/root>
VFS: fs_name = <romfs>
VFS: tried fs_name = <romfs> err= -6
*******
VFS: Cannot open root device "<NULL>" or unknown-block(31,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(31,0)
******************************************************************
Greg Ungerer a écrit :
Yes, it uses those.
uclinux.c map driver gives you the dynamic setup of your attached
ROMfs if you tacked it onto the end of your load image (that is
it sits in RAM at _ebss).
Regards
Greg
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
