> > I've applied your patch (from the second mail) and booted with the new > > kernel, using a m5 environment (don't have the m3 one at hand). > > Android starts exactly the same as before and freezes at the same > > place, the display stays blank. > > I'm wondering if that could be because of me using the m5 env. ? > > Yeah, sounds like the fb panning problem. M5 seems to be needing a > panable fb while m3 seems to get along without though it is also > complaining in the logs when the feature is missing. Maybe Digit can > comment on that .... please? Is that true or is there a way m5 runs on > a framebuffer whose virtual size equals the actual screen size? Right > now I don't care about tearing, I just want to see something.
I setup an m3 environment on the maemo and started android in that one using your m3 patch (and the binder from m5). The startup looks differently and I get 2 errors now: 18:45:31.912902 socket(PF_FILE, SOCK_STREAM, 0) = 3 18:45:31.914093 connect(3, {sa_family=AF_FILE, [EMAIL PROTECTED], 19) = -1 ECONNREFUSED (Connection refused) and the following more serious one: pid 2077] 18:45:34.457946 writev(3, [{"\4", 1}, {"runtime\0", 8}, {"Display startup: 1 devices\n\0", 28}], 3 <unfinished ...> [pid 2088] 18:45:34.459808 getpriority(PRIO_PROCESS, 0 <unfinished ...> [pid 2087] 18:45:34.460845 ioctl(6, 0xc0186201 <unfinished ...> [pid 2077] 18:45:34.461853 <... writev resumed> ) = 37 [pid 2088] 18:45:34.462585 <... getpriority resumed> ) = 30 [pid 2087] 18:45:34.463287 <... ioctl resumed> , 0x100ffda8) = 0 [pid 2102] 18:45:35.155273 syscall_983045(0x102fff80, 0, 0x20, 0, 0x102fff80, 0x14098, 0xa9d25ef9, 0xf0005, 0x100ffd90, 0xafe36e70, 0xa9d25ef9, 0x1, 0, 0x102fff68, 0xafe0b238, 0xafe0949c, 0x60000010, 0x102fff80, 0, 0, 0xc764, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 <unfinished ...> [pid 2077] 18:45:35.160156 getpid( <unfinished ...> [pid 2088] 18:45:35.161224 ioctl(6, 0xc0186201******** NO FRAMEBUFFER VSYNC WAIT IOCTL ************** <unfinished ...> ..... [pid 2077] 18:45:35.715148 writev(3, [{"\3", 1}, {"runtime\0", 8}, {"DisplayDevice::shutDown\n\0", 25}], 3) = 34 [pid 2077] 18:45:35.739685 writev(3, [{"\3", 1}, {"runtime\0", 8}, {"DisplayDevice::detach\n\0", 23}], 3) = 32 That's really strange as I'm using your patch...hmm > I can't access my webspace right now, but I'm sending you my m5 patch > via mail. Thanks, I'll test it now... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to android-internals@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---