Woodruff, Richard wrote:
I'm currently looking if Android can start on good old OMAP5912 OSK
with Mistral display [1]. The advantage (besides it is the only OMAP
board I have ;) ) is that it has a nice form factor, the buttons look
somehow like the Android emulator view and it is well supported by
kernel. The disadvantage is that it has only 32MB, I'm not sure if
this is sufficent to run Android.
That's neat.
Short update regarding my attempts to get Android m5-rc14 to run on OSK:
I use a script similiar to a.sh, and start runtime under strace control:
1) Just around
writev(3, [{"\4", 1}, {"SurfaceFlinger\0", 15}, {"SurfaceFlinger is
starting\0", 27}],3
the screen is *blanked* (no Android string, no red eye, just switched
to black). Similiar like when the screensaver is activated.
2) I get a
access("/dev/hw3d", R_OK) = -1 ENOENT (No such file or
directory)
but I think this doesn't matter.
3) Acessing /dev/alarm fails:
open("/dev/alarm", O_RDWR|O_LARGEFILE) = 6
ioctl(6, 0x40086104, 0xbea84c08) = -1 ENOTTY (Inappropriate
ioctl for device)
writev(3, [{"\5", 1}, {"runtime\0", 8}, {"Unable to read rtc, Not a
typewr"..., 38}], 7
writev(3, [{"\5", 1}, {"runtime\0", 8}, {"Invalid time detected, 0 set
to "..., 44}], 3
ioctl(6, 0x40086105, 0xbea84c08) = -1 ENOTTY (Inappropriate
ioctl for device)
writev(3, [{"\5", 1}, {"runtime\0", 8}, {"Unable to set rtc to
1167652800:"..., 51}], 0
close(6)
Hopefully this doesn't matter as well.
4) What really matters is:
open("/dev/binder", O_RDWR|O_LARGEFILE) = -1 ENXIO (No such device or
address)
writev(3, [{"\5", 1}, {"ProcessState\0", 13}, {"Opening
\'/dev/binder\' failed: No"...1
I have
# cat proc/devices | grep binder
251 binder
# ll dev/binder
crw-rw-rw- 1 root root 251, 58 Jan 1 00:03 dev/binder
and therefore I'm not really sure what's wrong here.
5) After some time system then reports
android_power_suspend: 437463043212
android sleep state 0->2 at 437463043212
active wake lock PowerManagerService
and a keypress results in
android_power_wakeup 2->0 at 1259669219970
android_power_suspend: done
so system is still alive ;)
I think major issue at the moment is the failing binder opening.
Dirk
-
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
