Re: [Ltib] How to get device nodes into zImage?

[Stuart Hughes]

Hi Ned,

I'm a bit confused here. zImage is normally just the kernel, the device
nodes come from whatever userspace package is selected.  The default for
imx27 is static.  You should see these in rootfs/dev/

When ramdisk or jffs2 image is made, the device nodes are not copied
from there, instead genext2fs takes the option -D (which is 
bin/device_table.txt) which is what it uses to create the device nodes
within the image.

As I said before, initramfs is coming to Savannah later.  However even
then we normally keep the kernel image and the userspace initramfs
separate (as for ramdisk or jffs2 image).  It is possible to combine
then (catted kernel+root) but generally we don't do this (some platforms
do IIRC).

Regards, Stuart

On Tue, 2008-11-18 at 00:50 -0800, Ned Konz wrote:
> I've been banging my head against this:
> 
> LTIB will make a zImage that contains most of the filesystem entries  
> you need to run your system.
> 
> Unfortunately, it lacks any device nodes (there are only a few empty  
> directories under /dev).
> 
> Later, a rootfs.ext2.gz may be produced that has all the proper device  
> entries in it.
> 
> How can we get the device entries in the zImage? I've tried pointing  
> the source for the INITRAMFS at the rootfs.tmp but it doesn't have the  
> device entries yet.
> 
> What is the best way to get a fully - populated ramdisk image into the  
> zImage -- with the device entries?
> 
> This is a lot easier than using a separate kernel image and rootfs  
> image.
>