There are three splashes as of 13 Nov. 2007. The U-Boot splash is displayed until the kernel takes over. Presumably the kernel will eventually display a splash while it boots. When userspace initializes, psplash displays a splash. Finally X displays a splash when it starts.

+

There are three boot screens (also called splashes or splash screens) as of 13 Nov. 2007. The [[U-Boot]] splash is displayed until the kernel takes over. Presumably the kernel will eventually display a splash while it boots. When userspace initializes, psplash displays a splash. Finally X displays a splash when it starts.

−

== U-boot Splash ==

+

=== [[U-Boot]] Splash ===

−

=== Original instructions ===

+

Werner's README states the following:

−

Is a raw framebuffer bitmap that is gzipped.

+

: "The splash image is a raw dump of the 480x640x16 frame buffer, with RGB

+

: 5:6:5 organization and HWSWP = 1. To save a lot of space and to greatly

+

: improve speed, we gzip the raw dump."

−

Here is a basic description: http://svn.openmoko.org/trunk/src/host/splash/README

This is already a part of the U-Boot image received in the phone... however, if you make changes to your splash image, you may need to change the splashimage variable to compensate!

+

−

+

−

0x5000 is the (maximum) size of the compressed file -- the splash.gz that gets created. If you've made changes to your image you may have increased the compressed size; if it exceeds 0x5000 (20480) bytes, the entire image will not load unless you increase this value in your splashimage U-Boot environment variable.

+

== Linux kernel ==

== Linux kernel ==

Line 40:

Line 68:

You need to recompile psplash, because the picture is hardcoded. There is a script in the source for psplash for making a new header file. On Ubuntu, you need the libgtk2.0-dev package to run the script.

You need to recompile psplash, because the picture is hardcoded. There is a script in the source for psplash for making a new header file. On Ubuntu, you need the libgtk2.0-dev package to run the script.

−

make-image-header.sh my_image.png HAND

+

make-image-header.sh my_image.png HAND

−

mv my_image-img.h psplash-hand-img.h

+

mv my_image-img.h psplash-hand-img.h

Then add your custom header to the OpenEmbedded recipe (org.openembedded.dev/packages/psplash/files/openmoko/psplash-hand-img.h), or rebuild psplash by hand.

Then add your custom header to the OpenEmbedded recipe (org.openembedded.dev/packages/psplash/files/openmoko/psplash-hand-img.h), or rebuild psplash by hand.

Line 49:

Line 77:

The X server accepts a -root-ppm option, which takes a plain old (raw) ppm file. Replace /usr/share/pixmaps/xsplash-vga.ppm on the phone or org.openembedded.dev/packages/xserver-kdrive-common/xserver-kdrive-common/openmoko/xsplash-vga.ppm in OpenEmbedded.

The X server accepts a -root-ppm option, which takes a plain old (raw) ppm file. Replace /usr/share/pixmaps/xsplash-vga.ppm on the phone or org.openembedded.dev/packages/xserver-kdrive-common/xserver-kdrive-common/openmoko/xsplash-vga.ppm in OpenEmbedded.

then enlightenment will try to start up with ''illume_init.edj'' for the splash

+

(the 'cylon' animated blip, or various other animations depending on image)

+

and will try to use ''/usr/share/enlightenment/data/themes/illume.edj'' as the

+

theme for illume. If it's E_PROFILE='-profile fso' then it looks for

+

''fso_init.edj'' splash and ''fso.edj'' theme, etc.

+

+

== See also ==

+

* [[Themes]]

+

* [[Edje]]

+

+

[[Category:Middleware settings]]

Latest revision as of 09:02, 10 February 2012

There are three boot screens (also called splashes or splash screens) as of 13 Nov. 2007. The U-Boot splash is displayed until the kernel takes over. Presumably the kernel will eventually display a splash while it boots. When userspace initializes, psplash displays a splash. Finally X displays a splash when it starts.

You need to recompile psplash, because the picture is hardcoded. There is a script in the source for psplash for making a new header file. On Ubuntu, you need the libgtk2.0-dev package to run the script.

The X server accepts a -root-ppm option, which takes a plain old (raw) ppm file. Replace /usr/share/pixmaps/xsplash-vga.ppm on the phone or org.openembedded.dev/packages/xserver-kdrive-common/xserver-kdrive-common/openmoko/xsplash-vga.ppm in OpenEmbedded.

/usr/share/enlightenment/data/init contains one or more .edj files
that each define an animated splash init that appears next, and until
enlightenment finishes loading. The .edj file used is determined by
$E_PROFILE. So if default_profile contains E_PROFILE='-profile illume'
then enlightenment will try to start up with illume_init.edj for the splash
(the 'cylon' animated blip, or various other animations depending on image)
and will try to use /usr/share/enlightenment/data/themes/illume.edj as the
theme for illume. If it's E_PROFILE='-profile fso' then it looks for
fso_init.edj splash and fso.edj theme, etc.

Views

Personal tools

There are three splashes as of 13 Nov. 2007. The U-Boot splash is displayed until the kernel takes over. Presumably the kernel will eventually display a splash while it boots. When userspace initializes, psplash displays a splash. Finally X displays a splash when it starts.

This is already a part of the U-Boot image received in the phone... however, if you make changes to your splash image, you may need to change the splashimage variable to compensate!

0x5000 is the (maximum) size of the compressed file -- the splash.gz that gets created. If you've made changes to your image you may have increased the compressed size; if it exceeds 0x5000 (20480) bytes, the entire image will not load unless you increase this value in your splashimage U-Boot environment variable.

Linux kernel

To Do

psplash

You need to recompile psplash, because the picture is hardcoded. There is a script in the source for psplash for making a new header file. On Ubuntu, you need the libgtk2.0-dev package to run the script.

Then add your custom header to the OpenEmbedded recipe (org.openembedded.dev/packages/psplash/files/openmoko/psplash-hand-img.h), or rebuild psplash by hand.

X splash

The X server accepts a -root-ppm option, which takes a plain old (raw) ppm file. Replace /usr/share/pixmaps/xsplash-vga.ppm on the phone or org.openembedded.dev/packages/xserver-kdrive-common/xserver-kdrive-common/openmoko/xsplash-vga.ppm in OpenEmbedded.