HI!
The problem was with SDRAM memory. My kernel saw only 24 M SDRAM of
128 M available on the platform.
You can see it at the beginning of linux kernel start, it prints:
Total memory: ___, and available memory:___.
So you need a lot of available memory. In my case Android started
working after i g
I am trying to boot android with 2.6.32 kernel.My system is crashing at the
same place.
My crash log_
[ 31.218688] WARNING: at kernel/workqueue.c:485
flush_cpu_workqueue+0x30/0xb0()
[ 31.225982] Modules linked in:
[ 31.229125] [] (unwind_backtrace+0x0/0xdc) from []
(warn_slowpath_common+0x4
Thanks!
I already added pan function to my framebuffer driver, but seems
something goes wrong.
Screen is blinking too much.
Also i fixed touch screen, now it works!
On Mar 30, 9:20 am, Qipeng wrote:
> Congratulation!
>
> According to goldfishfb.c in android kernel, you may add the 'pan'
> functi
Congratulation!
According to goldfishfb.c in android kernel, you may add the 'pan'
function to solve the blinking.
For touchscreen, try to make sure your driver is ok, and get more
information from Eventhub.cpp in SourceCode.
Good luck.
On Mar 30, 3:41 am, supermaximus79 wrote:
> Thanks a lot A
Thanks a lot Abukustafan!
Today i at last started android on my platform.
What i can say, screen is blinking, and touchscreen doesn't work at
all.
Do you have the same problems on your platform?
How to make touch screen work?
Thanks again!
Best wishes!
On Mar 29, 4:10 am, abukustfan wrote:
>
Hi,
Yes, pmem and android power are not necessary for android.
I also did not enable these for my platform.
On Mar 26, 8:54 pm, supermaximus79 wrote:
> Hi!
> I use init.rc which android builds with ramdisk.img.
> I a little modified init.rc - set loglevel to 6.
> Also my kernel doesn't have driv
May be i add not enought partitions on my nand flash? or not enought
sized?
Right now i have only 4 partitions:
init: mtd partition 0, u-boot (374 kb)
init: mtd partition 1, kernel (3m)
init: mtd partition 2, system (85m)
init: mtd partition 3, userdata (39m)
Is it correct?
On Mar 26, 1:54 pm, s
Hi!
I use init.rc which android builds with ramdisk.img.
I a little modified init.rc - set loglevel to 6.
Also my kernel doesn't have driver pmem, and android power. But i red
that this driver is not necessary for android. isn't it?
On Mar 26, 6:20 am, Neo wrote:
> I feel some of your kernel conf
I feel some of your kernel configs could be off.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
To unsubscribe from this group, send email to
android-porting+unsubscribegooglegroups.com or reply to this email with the
words
Hi,
seem your framebuffer driver is fine. At least it did not hang on
"page flipping not supported".
Now, I thinks the problem is here.
> > select 1714 (sh), adj 0, size 34, to kill
> > select 1715 (servicemanager), adj 0, size 38, to kill
> > select 1716 (vold), adj 0, size 57, to kill
> > selec
Hello guys!
Could you tell me please, what do you think about log meggases in my
previous letter?
In previous messages you told that framebuffer driver for android must
have double buffering.
I found in the internet some articles which describe android frame
buffer.
Here they are:
http://pdk.andro
Hello everybody!
I think i realized page flipping in my s3c-fb driver. It's a Ben Dooks
driver for s3c platforms.
I set double size to virtual_yres, double size to smem_len, and
implemented s3c_fb_pan_display function.
The log messages are changed!!! Here they are:
As you can see some crash appea
I think so.
and furthermore, please look at what is in /dev/graphics/.
maybe you also have to make a symbol link of the device name.
On Mar 23, 8:19 am, abukustfan wrote:
> Hi,
>
> you kernel need to support double frame buffer if you use eclair or
> latest.
> check you frame buffer driver.
>
> G
your bootup is stuck right at surface flinger init, next step will be
fb creation and overlay init..
and ya, as abukustfan said below, eclair needs bigger frame buffer
allocated explicitly.
check your fb driver or it might be possible to pass fb size via bootargs.
PS.
similar discussion on eclair
Hi,
you kernel need to support double frame buffer if you use eclair or
latest.
check you frame buffer driver.
Good luck.
On Mar 22, 6:08 pm, supermaximus79 wrote:
> full logcat message i posted on 19 of march
>
> On 22 мар, 08:10, Deva R wrote:
>
>
>
> > looks like some ioctl call to kernel i
full logcat message i posted on 19 of march
On 22 мар, 08:10, Deva R wrote:
> looks like some ioctl call to kernel is returning error (fopen error
> due to missing sysfs entry)..
> can you post complete logcat log (do 'logcat &' once u get '#' shell)
>
> 2010/3/21 supermaximus79 :
>
> > No, it is
looks like some ioctl call to kernel is returning error (fopen error
due to missing sysfs entry)..
can you post complete logcat log (do 'logcat &' once u get '#' shell)
2010/3/21 supermaximus79 :
> No, it is not looping. After messages:
>> libandroid_servers.so 0x0
>> D/dalvikvm( 1742): Added shar
No, it is not looping. After messages:
> libandroid_servers.so 0x0
> D/dalvikvm( 1742): Added shared lib /system/lib/libandroid_servers.so
> 0x0
> E/BatteryService( 1742): Could not open /sys/class/power_supply
> I/sysproc ( 1742): Entered system_init()
> I/sysproc ( 1742): ServiceManager: 0x13cbd0
Is it just looping there? What happens after surface flinger loads?
On Mar 19, 9:04 am, supermaximus79 wrote:
> Hello!
> After spending two days i fixed problems with ALSA sound, and
> vold.conf.
> I still can't run Android on my platform. it hangs.
>
> Please, help me to understand, why android
Hello!
After spending two days i fixed problems with ALSA sound, and
vold.conf.
I still can't run Android on my platform. it hangs.
Please, help me to understand, why android doesn't start on my board?
New log messages:
I/vold( 1728): Android Volume Daemon version 2.0
I/DEBUG ( 1729): debugg
Thanks everybody!
Right now i am fixing my sound chip driver to get alsa work.
You are right regarding vold.conf, there is no such file in my
filesystem.
And of course /sys/class/mmc_host path wrong.
I should modify vold.conf from generic build and add it to my
platform, but it'll be after succe
It looks like there might be some problem int the vold.conf file, make
sure the path /sys/class/mmc_host is correct.
On Mar 16, 8:39 pm, supermaximus79 wrote:
> # logcat log
> I/vold ( 1708): Android Volume Daemon version 2.0
> E/vold ( 1708): Unable to open '/sys/class/mmc_host' (No such
agree. Try disable ALSA.
On Mar 17, 3:55 am, Deva R wrote:
> see, there you go.., ALSA is broken - not sure why, probably due to
> interface break with kernel..
>
>
>
> > E/ALSALib ( 1712): external/alsa-lib/src/control/control.c:909:
> > (snd_ctl_open_noupdate) Invalid CTL AndroidOut
> > W/Aud
see, there you go.., ALSA is broken - not sure why, probably due to
interface break with kernel..
> E/ALSALib ( 1712): external/alsa-lib/src/control/control.c:909:
> (snd_ctl_open_noupdate) Invalid CTL AndroidOut
> W/AudioHardwareALSA( 1712): Unable to attach mixer to device
> AndroidOut: No such
# logcat log
I/vold( 1708): Android Volume Daemon version 2.0
E/vold( 1708): Unable to open '/sys/class/mmc_host' (No such file
or directory)
E/vold( 1708): Unable to open '/sys/class/switch' (No such file or
directory)
D/vold( 1708): Bootstrapping complete
I/DEBUG ( 1709): debugg
not sure why.. logcat log??
On Tue, Mar 16, 2010 at 6:16 PM, supermaximus79 wrote:
> Hi.
> You are right. Kernel panic was because my 2.6.31 kernel didn't have
> ASHMEM driver, i found it in core/init/ source files. The good news is
> that ASHMEM driver is the same for all linux kernels from 6.27
Hi.
You are right. Kernel panic was because my 2.6.31 kernel didn't have
ASHMEM driver, i found it in core/init/ source files. The good news is
that ASHMEM driver is the same for all linux kernels from 6.27 to
6.32. So yesterday i added ASHEMEM driver to my 2.6.31 kernel and it
works. No Kernel Pan
Did you add ash memory to your kernel?
On Mar 13, 3:37 am, Максим Андрущенко wrote:
> Hello!
>
> I am porting Android on s3c6410 compatible platform. So, using Android
> sources, i created platform's profile, and compiled ramdisk.img, system.img,
> userdata.img.
>
> I use 2.6.31-rc4 kernel, in
28 matches
Mail list logo
