> 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 can't access my webspace right now, but I'm sending you my m5 patch via mail. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
