-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Hi list, | | There is a short period of white screen after kernel boots. It is due | to that the glamo driver is initializing and the backlight is already | turned on by u-boot: | | ... | [ 0.865000] glamo3362 glamo3362.0: Detected Glamo core 3650 Revision 0002 (49 | -> screen turns white in glamo_init_script | [ 0.905000] glamo3362 glamo3362.0: Glamo core now 49119232Hz CPU / 81887232Hz | [ 0.905000] Detected S-Media IRQ# pullup, enabling interrupt | [ 1.005000] glamo-spi-gpio glamo-spi-gpio.0: registering c039bb50: jbt6k74 | [ 1.035000] SMEDIA Glamo frame buffer driver (C) 2007 Openmoko, Inc. | -> screen turns black after glamofb_set_par | [ 1.640000] Console: switching to colour frame buffer device 80x58 | ... | | My idea is to avoid re-initialization if uboot has already done it. Is | it sound ok? | | BTW, the glamofb initializes the 4MB memory allocated to it during | initialization. It takes about 0.5 seconds. The attached patch cuts it | down to 0.1 seconds by only initializing the part used for framebuffer.
The patch sounds good, thanks. But the problems with white screen on boot are going to be solved a better way: Qi does not turn on the backlight and when the balaji-tracking stuff is used the backlight device is a child of the framebuffer, meaning the backlight will not be initialized until the framebuffer has been initialized. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkLFhIACgkQOjLpvpq7dMqU6QCfcbbPDkyM7xPwUldzrcg9BYZA s6IAn3bEoch2x3PW/NuA7sJ8XsZfC3P5 =aufI -----END PGP SIGNATURE-----
