Specifications

-rwxr-xr-x 1 root root 1152054 Feb 8 2012 slide-2.bmp
-rwxr-xr-x 1 root root 1152054 Feb 8 2012 slide-3.bmp
-rwxr-xr-x 1 root root 1152054 Feb 8 2012 slide-4.bmp
-rwxr-xr-x 1 root root 1152054 Feb 8 2012 slide-5.bmp
-rwxr-xr-x 1 root root 1152054 Feb 8 2012 slide-6.bmp
-rwxr-xr-x 1 root root 1152054 Feb 8 2012 slide-7.bmp
-rwxr-xr-x 1 root root 1152054 Feb 8 2012 slide-8.bmp
-rwxr-xr-x 1 root root 2340744 Apr 18 07:07 uImage
root@generic-armv5te:/tmp/duts#
unmount the partition with:
root@generic-armv5te:/tmp/duts# umount /tmp/duts/mmc
root@generic-armv5te:/tmp/duts# mount
rootfs on / type rootfs (rw)
192.168.1.1:/opt/eldk-5.2.1/armv5te/rootfs-lsb-sdk/ on / type nfs (rw,relatime,vers=3,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.1,mountvers=3,mountproto=tcp,local_lock=all,addr=192.168.1.1)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /dev type tmpfs (rw,relatime,mode=755)
/dev/mmcblk0p2 on /media/mmcblk0p2 type vfat (rw,sync,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/mmcblk0p3 on /media/mmcblk0p3 type ext4 (rw,sync,relatime,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /var/volatile type tmpfs (rw,relatime)
tmpfs on /media/ram type tmpfs (rw,relatime)
root@generic-armv5te:/tmp/duts# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 330279532 155153328 158348988 50% /
192.168.1.1:/opt/eldk-5.2.1/armv5te/rootfs-lsb-sdk/ 330279532 155153328 158348988 50% /
none 127104 140 126964 1% /dev
/dev/mmcblk0p2 30642 12666 17976 42% /media/mmcblk0p2
/dev/mmcblk0p3 1781936 1187500 503916 71% /media/mmcblk0p3
tmpfs 127104 172 126932 1% /var/volatile
tmpfs 127104 0 127104 0% /media/ram
root@generic-armv5te:/tmp/duts#
9.4. Splash Screen Support in Linux
To complement the U-Boot Splash Screen feature the new configuration option
"CONFIG_FB_PRE_INIT_FB" was added to the Linux kernel. This allows the Linux kernel to skip certain
parts of the framebuffer initialization and to reuse the framebuffer contents that was set up by the U-Boot
firmware. This allows to have an image displayed nearly immediately after power-on, so the delay needed to
boot the Linux kernel is masked to the user.
The current implementation has some limitations:
We did not succeed in reusing the previously allocated framebuffer contents directly. Instead, Linux
will allocate a new framebuffer, copy the contents, and then switch the display. This adds a minimal
delay to the boot time, but is otherwise invisible to the user.
•
Linux manages its own colormap, and we considered it too much effort to keep the same settings as
used by U-Boot. Instead we use the "trick" that U-Boot will fill the color map table backwards (top
down). This works pretty well for images which use no more than 200...225 colors. If the images uses
more colors, a bad color mapping may result.
We strongly recommend to convert all images that will be loaded as Linux splash screens to use no
more than 225 colors. The "ppmquant" tool can be used for this purpose (see Bitmap Support in
U-Boot for details).
•
Usually there will be a Linux device driver that is used to adjust the brightness and contrast of the
display. When this driver starts, a visible change of brightness will happen if the default settings as
used by U-Boot differ.
•
9.4. Splash Screen Support in Linux 110