I'm not sure if this is related to the question, but there's a
"tombstone_00" in the data partition. It starts with
Build fingerprint: 'generic/generic/generic/:1.0/TC3/eng.hdante.
20081126.191248:eng/test-keys'
pid: 385, tid: 397 >>> system_server <<<
signal 11 (SIGSEGV), fault addr 00000008
r0 00000000 r1 40000000 r2 40000000 r3 00000000
r4 00087b00 r5 00000000 r6 00000004 r7 00087238
r8 44868dbc r9 afe35d78 10 a9d2760d fp 00000001
ip acd35a84 sp 45b68e20 lr acd2035b pc ac420364 cpsr 00000030
#00 pc ac420364 /system/lib/libui.so
#01 pc acd20358 /system/lib/libsurfaceflinger.so
#02 pc a9d2787c /system/lib/libutils.so
#03 pc a9d27674 /system/lib/libutils.so
#04 pc afe0ed48 /system/lib/libc.so
#05 pc afe0e8bc /system/lib/libc.so
code:
ac420354 fc3cf001 bd30b001 1c03b500 1c0ab081
ac420364 1c196880 fbe0f001 bd00b001 1c03b500
stack:
45b68de0 afe35d78
45b68de4 80100004
45b68de8 45b68e0c
45b68dec 00087b00 [heap]
(...)
On 27 nov, 19:24, Henrique Dante de Almeida <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I hope to start to convert the userspace code soon, but before I
> begin, maybe you could help me with a doubt.
>
> I'm currently starting android in palmtx and it seems to be correctly
> loading the vm (lots of files and directories are created in the data
> partition), but I only get a blank screen. I supposed this was due to
> the lack of double buffering support in the PXA framebuffer driver,
> but even after applying the "pan" patch, the screen is still blank.
>
> Could this be caused by the lack of PM code (I currently have all
> android PM code disabled) ? Or the lack of power management wouldn't
> cause a blank screen ?
>
> Thanks,
>
> On 21 nov, 18:29, "Mike Chan" <[EMAIL PROTECTED]> wrote:
>
> > The power API changed in 2.6.27
>
> > Your best bet is to modify the userspace framework code to use the new
> > api's exposed in
>
> > /sys/power/*
> > state
> > wake_lock
> > wake_unlock
> > wait_for_fb_sleep
> > wait_for_fb_wake
>
> > on the device.
>
> > Look at these files and replace the old references with the new one.
>
> > libs/hardware/power/power.c
> > servers/surfaceflinger/DisplayHardware/DisplayHardwareBase.cpp
> > system/rootdir/init.rc
>
> > Or you could try to port the ARCH specific bits you need into 2.6.25...
>
> > On Fri, Nov 21, 2008 at 11:08 AM, Henrique Dante de Almeida
>
> > <[EMAIL PROTECTED]> wrote:
>
> > > Hello,
>
> > > I've noticed that there's a new branch in android repository,
> > > "android-2.6.27". I was interested in this version, because I'm trying
> > > to port Android to a certain hardware that this kernel version
> > > supports (Palm TX). However, that branch doesn't appear to be a simple
> > > upgrade to 2.6.27. Instead there appears to be changes in the android
> > > code (in particular there's no "android power" module). Is this
> > > correct ?
>
> > > - Will the current repository (as a whole, not only the kernel)
> > > require changes to work with the new kernel ?
> > > - I would like to do this port as a final project for my OS classes,
> > > so the deadline is short (two weeks). Should I take the changes from
> > > 2.6.25 and create my own port for 2.6.27, so that the rest of the
> > > system still works ?
>
> > > Thanks,
>
> > --
> > MIke Chan
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [EMAIL PROTECTED]
website: http://groups.google.com/group/android-kernel
-~----------~----~----~----~------~----~------~--~---
