![]() |
![]() |
![]()
Post
#1
|
|
Group: Members Posts: 4 Joined: 24-January 08 Member No.: 21,256 ![]() |
Hi everyone:
Does anyone can help me? Thanks in advance. I'm now working on porting m5rc14 to our platform. I meet 2 problems: 1) when system starts, console seem almost hangs. and process system_server occupies 99% of CPU time. This is my logcat: W/AudioFlinger( 557): Using stubbed audio hardware. No sound will be produced. I/AudioFlinger( 557): AudioFlinger's main thread ready to run. I/ServiceManager( 539): ServiceManager: addService(AudioFlinger, 0x133f8) I/sysproc ( 557): System server: starting Android runtime. I/sysproc ( 557): System server: starting Android services. I/SystemServer( 557): Entered the Android system server! I/sysproc ( 557): System server: entering thread pool. D/TouchDex( 557): TouchDex parent waiting for pid=580 (timeout=36.4s) I/ServiceManager( 539): ServiceManager: unable to find service activity I/runtime ( 539): Still waiting for activity manager... I/ServiceManager( 539): ServiceManager: waiting for service activity D/AudioFlinger( 557): Audio hardware entering standby I/ServiceManager( 539): ServiceManager: unable to find service activity I/runtime ( 539): Still waiting for activity manager... I/ServiceManager( 539): ServiceManager: waiting for service activity I/ServiceManager( 539): ServiceManager: unable to find service activity I/runtime ( 539): Still waiting for activity manager... I/ServiceManager( 539): ServiceManager: waiting for service activity I/ServiceManager( 539): ServiceManager: unable to find service activity I/runtime ( 539): Still waiting for activity manager... I/ServiceManager( 539): ServiceManager: waiting for service activity I/ServiceManager( 539): ServiceManager: unable to find service activity I/runtime ( 539): Still waiting for activity manager... I/ServiceManager( 539): ServiceManager: waiting for service activity I/ServiceManager( 539): ServiceManager: unable to find service activity I/runtime ( 539): Still waiting for activity manager... I/ServiceManager( 539): ServiceManager: waiting for service activity I/ServiceManager( 539): ServiceManager: unable to find service activity I/runtime ( 539): Still waiting for activity manager... I/ServiceManager( 539): ServiceManager: waiting for service activity E/TouchDex( 557): timed out waiting for 580; kill(0) returns 0 It seems services don't respond to SeviceManager, it doesn't happen on previous version 2). There's nothing appear on the screen. (screen is turned to black, it doesn't happen on previous version, too) m3rc37 system runs well on our platform with new released kernel. |
|
|
![]() |
![]()
Post
#2
|
|
![]() Group: Members Posts: 373 Joined: 18-March 04 From: The Netherlands Member No.: 2,380 ![]() |
I did it, it works! The problem was the unsupported page flipping in the frame buffer.
More info later, it needs some more tweaking before I can upload a new image. Check out my blog for more info. |
|
|
![]()
Post
#3
|
|
![]() Group: Members Posts: 217 Joined: 12-February 06 From: Tokyo Member No.: 9,124 ![]() |
>>More info later, it needs some more tweaking before I can upload a new image.
WOW~~! Looking forward to it! |
|
|
![]()
Post
#4
|
|
Group: Members Posts: 45 Joined: 30-December 07 From: Japan Member No.: 21,136 ![]() |
Today I implemented my version of double buffer and pan in pxafb. It works. m5_rc14 booted up on my Zaurus finally. My patch is very primitive. Any suggestions make it better are very welcome.
o Android Zaurus: m5_rc14 works on my Zaurus C3000 Cortez, Is your keyboard working correctly? Something funny with mine. I can't navigate on the menu by cursor keys. It's like a jumping around. |
|
|
![]()
Post
#5
|
|
Group: Members Posts: 17 Joined: 2-October 06 Member No.: 11,617 ![]() |
Today I implemented my version of double buffer and pan in pxafb. It works. m5_rc14 booted up on my Zaurus finally. My patch is very primitive. Any suggestions make it better are very welcome. o Android Zaurus: m5_rc14 works on my Zaurus C3000 It works for me too. Just a litle thing in your patch, your panning function only toggle FB base adresse. The result can be inverted. Normaly the base adresse is calculated with the var.yoffset value from var_screeninfo. I'm going to work on that ! Thanks ! |
|
|
![]()
Post
#6
|
|
Group: Members Posts: 45 Joined: 30-December 07 From: Japan Member No.: 21,136 ![]() |
Normaly the base adresse is calculated with the var.yoffset value from var_screeninfo. I'm going to work on that ! Big thanks from me. I'm not familliar with fb driver. Please make the patch better. I noticed that some long cycle flickerings while I tried a couple of times booting Android up. I guess I need exclusiveness to change DMA address. |
|
|
![]() ![]() |
![]() |
Lo-Fi Version | Time is now: 24th April 2018 - 03:11 AM |