As for initrd , sure , the bootm command in U-Boot takes up to three arguments:
bootm <kernel uImage address> <initrd address> <FDT blob address>
So if you want your initrd to be passed to kernel , just supply the second argument.
Of course, you can also use initramfs and build the ramdisk into the kernel image if needed be. That's possible if you run 'make menuconfig' in the kernel source tree, navigate into 'General setup' -> 'Init RAM filesystem and RAM disk...' , check it and put path to your initramfs root dir into 'Initramfs source file(s)' . Note that if you have any /dev/ nodes in your initramfs's /dev/ , you might want to read Documentation/filesystems/ramfs-rootfs-initramfs.txt (you might want to read that anyway) section 'Populating initramfs' ...
As for initrd , sure , the bootm command in U-Boot takes up to three arguments:
bootm <kernel uImage address> <initrd address> <FDT blob address>
So if you want your initrd to be passed to kernel , just supply the second argument.
Of course, you can also use initramfs and build the ramdisk into the kernel image if needed be. That's possible if you run 'make menuconfig' in the kernel source tree, navigate into 'General setup' -> 'Init RAM filesystem and RAM disk...' , check it and put path to your initramfs root dir into 'Initramfs source file(s)' . Note that if you have any /dev/ nodes in your initramfs's /dev/ , you might want to read Documentation/filesystems/ramfs-rootfs-initramfs.txt (you might want to read that anyway) section 'Populating initramfs' ...
Bill
We are sorry for getting back to you so late. Are you still stuck with the issue? If you have somehow to resolved the
issue, can we close the discussion? If you still need Freescale help, please feel free to contact us.
Thanks,
Yixing