Hi all -

We are running 4.1.2 on an OMAP4460 platform made by Variscite:
http://www.variscite.com/products/system-on-module-som/cortex-a9/var-som-om44-cpu-ti-omap-4-omap4460

We initially were using ICS (4.0.3) on this platform and we had a working 
/initlogo.rle file that would display on startup before the boot animation. 
 Now that we have moved to JB, this no longer works.

After tracing the code of logo.c 
(https://android.googlesource.com/platform/system/core/+/android-4.1.2_r2/init/logo.c)
 
we also noticed that even with the initlogo.rle file missing from the 
rootfs, the boot log does not output the expected "cannot open 
'/initlogo/rle'" error message.  So it is as if the init process never 
attempts to load the image file on JB, but the AOSP code in this regard 
does not seem to have changed from one version to the other.

The only other code that would execute in logo.c before attempting to read 
the image is vt_set_mode(), which apparently attempts to open /dev/tty0 and 
configure it.  Our device running JB does not look to have a /dev/tty0 
node, and so perhaps that is where the issue is occurring?  If so, what do 
we need to do in the kernel to re-active /dev/tty0?

How can we get our boot image to display on a JB system?

Thanks in advance!

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to