Does uInitrd need to be recompiled every time kernel is recompiled?

Dear experts,

I managed to get Ubuntu 10.04 working properly on Devkit8000 but
failed to get 11.04 working. Will work on that later. Now, I have made
minor modifications to the kernel. No drivers have been added. After
recompiling the kernel, I cannot find uInitrd. No problem with
uImage.

May I know whether uInitrd needs to be generated every time the kernel
is modified and recompiled or is it necessary only when big changes
have been made?

Any other ways to generate uInitrd other than the following;

- Boot the beagle with your uImage, or fire up a qemu
machine with the same rootfs.

then run: "update-initramfs -c -k 2.6.xx-xx" to get the
initrd.img-2.6.xx-xx file, then run mkimage on the
initrd.img-2.6.xx-xx for use with u-boot..

No, especially when you control the options in uImage, as long as the
"uImage" self can boot the root file system and load the needed
modules by it's self.. In fact in a lot of cases you don't even need
the uInitrd, in ubuntu with the beagle it does a couple useful things,
so if you don't care about the 1970 clock setting or extra warnings on
boot, you can remove it..

Regards,

> Dear experts,

> I managed to get Ubuntu 10.04 working properly on Devkit8000 but
> failed to get 11.04 working. Will work on that later. Now, I have made
> minor modifications to the kernel. No drivers have been added. After
> recompiling the kernel, I cannot find uInitrd. No problem with
> uImage.

> May I know whether uInitrd needs to be generated every time the kernel
> is modified and recompiled or is it necessary only when big changes
> have been made?

No, especially when you control the options in uImage, as long as the
"uImage" self can boot the root file system and load the needed
modules by it's self.. In fact in a lot of cases you don't even need
the uInitrd, in ubuntu with the beagle it does a couple useful things,
so if you don't care about the 1970 clock setting or extra warnings on
boot, you can remove it..

Thank you, Sir! This is good news. I was thinking how I can reduce the
boot-up time. Removing the uInitrd will certainly save a lot of time
for the boot-up process.

To remove uInitrd, is it just a matter of removing changing "fatload
mmc 0:1 0x81600000 uInitrd;" from bootcmd for the u-boot? Something
like that?