question on /dev devices

[jean-philippe francois]

>
> echo -n " Mounting /proc             : "
> mount -n -t proc /proc /proc
> status $? 1
>
> echo -n " Mounting /sys              : "
> mount -n -t sysfs sysfs /sys
> status $? 1
>
> echo -n " Mounting /dev              : "
> mount -n -t tmpfs mdev /dev
> status $? 1
>
Here you are mounting a tmpfs on /dev
Further access to /dev goes to this tmpfs, not to flash

> echo -n " Mounting /dev/pts          : "
> mkdir /dev/pts
> mount -t devpts devpts /dev/pts
> status $? 1
>
> echo -n " Enabling hot-plug          : "
> echo "/sbin/mdev" > /proc/sys/kernel/hotplug
> status $? 0
>
> echo -n " Populating /dev            : "
> mkdir /dev/input
> mkdir /dev/snd
>
> mdev -s
> status $? 0
>
mdev -s is responsible for populating /dev/ with the initial device
exposed by the kernel.
device exists in the kernel without the /dev filesystem
The /dev representation is a way for userspace to access
devices in that lives in kernelspace.

mdev should certainly not take 5 sec to populate /dev.
If you want a faster /dev/ population, you can use devtmpfs.
 - Choose the DEVTMPFS option in your kernel config.
 - mount -t devtmpfs devtmpfs /dev in your script
 - keep the hotplug mechanism
 - remove the mdev -s line.

For fast boot time :
set verify=n in u-boot
use uncompressed kernel and initramfs
enable timing informations on printk for easier debugging
try to get as small as possible kernel and initramfs


> i want fast boot right now i did it using jffs2 image and time is about 13seconds from ubl to linux prompt with all the services up and running.
>
> does doing alot of insmod and mknod on the jffs2 image affects the life of the flash?
>
> regard's
> RT
>
> _______________________________________________
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source at linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>