Hi,
Do you know that how can I generate a big-endian cramfs ramdisk under Intel's PC? By default its in little-endian format and mkfs.cramfs has no option to change it... Because from u-boot source code file -- common/cmd_bootm.c do_bootm_linux() function, it seems pointer data (line 851) is NULL so the loading ramdisk to memory's code desn't running. So, I think that its my ramdisk format's problem...
my u-boot (v1.2.0) didn't load my ramdisk into memory, I guess its ramdisk format's problem maybe. $file rootfs rootfs: Linux Compressed ROM File System data, little endian size 4513792 version #2 sorted_dirs CRC 0x661454d0, edition 0, 2662 blocks, 471 files
Below is the runtime u-boot message: => tftpboot a0800000 uRamdisk => iminfo a0800000 ## Checking Image at a0800000 ... Image Name: Test Ramdisk Image Created: 2008-12-17 11:43:47 UTC Image Type: MIPS Linux RAMDisk Image (gzip compressed) Data Size: 3824687 Bytes = 3.6 MB Load Address: 82010000 Entry Point: 82010000 Verifying Checksum ... OK => bootm bfc60000 a0800000 ## Booting image at bfc60000 ... Image Name: MIPS OpenWrt Linux-2.6.21.7 Created: 2008-12-16 19:55:08 UTC Image Type: MIPS Linux Kernel Image (gzip compressed) Data Size: 1172251 Bytes = 1.1 MB Load Address: 80010000 Entry Point: 80262000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading Ramdisk Image at a0800000 ... Image Name: Test Ramdisk Image Created: 2008-12-17 11:21:06 UTC Image Type: MIPS Linux RAMDisk Image (gzip compressed) Data Size: 3824687 Bytes = 3.6 MB Load Address: 82010000 Entry Point: 82010000 Verifying Checksum ... OK /* COMMENT ADDED BY MIKE, boot loader hasn't loaded RAMDISK since no "Loading Ramdisk to..." output...... */
Starting kernel ...
LINUX started... ... No filesystem could mount root, tried: cramfs squashfs romfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
Any suggestions will be greate appreciated !
Best regards, Mike