Hello All,
What is the minimum configuration to run android ?
On the website
http://www.kandroid.org/android_pdk/system_requirements.html
They have described anything about processor speed.
We have a processor arm9 300 mhz. memory is not a constraint . Would it be
enough for running android
It depends on many parameters - e.g. a relatively slow CPU can be OK
if it's got enough cache and/or fast RAM and/or much RAM and/or fast
storage and/or fast graphics. a...@300 might do it if it's in good
conditions, but the only way to know is to port and see how usable the
result looks.
JBQ
Hi,
I can zip up the existing bionic and kernel modifications for
download, if someone could help me troubleshoot this error.
Elvis
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:
I don't know what is this command for...and it seems that no documentation
can be found
I'm wandering it has something to do with the virtual space allocation
I know that the space allocation in our arch is different from the standard
linux kernel
So do i need to edit the map file?
And how to
I found that aprioir is a tool for prelink
And I think unable this process won't influence the compiling process expect
future performance...
On Mon, Jul 27, 2009 at 2:46 PM, Ouyang Jiannan jallen@gmail.comwrote:
I don't know what is this command for...and it seems that no documentation
Dear all:
For standard Linux kernel, a driver normally need to implement
suspend/resume callbacks to be called when system suspend.
For android kernel, a some driver may also call
android_register_early_suspend to register some additional callbacks such
as:
559
Hi fadden,
Thank you for your reply.
yes, maybe it is the cause at you said.
About the memPartAlloc message, I think I found out the root cause and
I would like to share with you and would like to have some idea from
you.
At you know, at the current Dalvik allocates heap memory by mmap and
Recently the upstream has merged donut into the master branch.
Unfortunately, it breaks our Android-x86 build. We are still trying to
figure out how to fix that. But the changes are so huge, we cannot fix
it very soon. In the meantime, you can get a stable branch by:
$ repo init -u
Hi It's my first posting.
I am porting a ntive c application to android phone to share with
windows machine.
My compile error messages show that the source code needs struct
dirent64 but it is missing in bionic/libc/include/dirent.h which is
the only one included when compiled but in
I am currently trying to build both adb and gadget support into an
Android kernel.
Kernel was originally 2.6.27.10 but I believe it has been patched by a
third party and therefore I'm unsure where it is now.
I have tried building the g_serial.ko and g_android.ko modules to be
loaded dynamically
Hello all,
I have a Motorola A810 that is based on OMAP730/850..
There are a couple of videos on A810s that have been ported to
Android..
Could you please guide me on the steps involved in a generic port?
I've looked for the FAQs talked about in the group's introduction but
haven't been able to
On Jul 26, 10:33 pm, louis dmq...@gmail.com wrote:
My compile error messages show that the source code needs struct
dirent64 but it is missing in bionic/libc/include/dirent.h which is
the only one included when compiled but in bionic/libc/kernel/common/
linux/dirent.h which is not included
On Jul 27, 4:49 am, Mercury bao...@gmail.com wrote:
Could you please advice me why I call free as the above implement
cause crash?
I don't know.
If possible, could you tell me or share me a document about the design
of heap implement in Dalvik?
There isn't one. It uses the dlmalloc mspace
On Jul 26, 10:10 am, Elvis Dowson elvis.dow...@gmail.com wrote:
I'm getting this error with linux-omap3-2.6.31:
E/dalvikvm( 676): ERROR: Byte swap + verify failed
[...]
E/dalvikvm( 670): ERROR: Bad length: expected 818624000, got 3590960
In hex, those are 0x30cb3600 and 0x36cb30,
I have seen the source tree about android-x86.I found that there is
vendor/asus folder and my board is freescale MX27,and i don't have a
vendor folder .Can i use the vendor/asus folder straightly ?
--~--~-~--~~~---~--~~
unsubscribe:
I have port android on my cortex success,but only using demo image.
now I want to porting alsa on my board.but I met a problem. hope
anyone can help me .
I only git alsa_sound(/hardware) and alsa-lib(/external).and modify
the BoardConfig.mk(using alsa).
but now I can't boot up. when i execute
besides,I want to ask you how can I know the problem on my porting.
now I noly know using minicom to boot up.
what else command I could know why I can't go into desktop.
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:
Hi,
Please walk through the logcat output.
Warm Regards,
Anil
On Tue, Jul 28, 2009 at 9:19 AM, WenXing wenxingxing2...@126.com wrote:
besides,I want to ask you how can I know the problem on my porting.
now I noly know using minicom to boot up.
what else command I could know
Hi, I encountered a similar error, see
http://groups.google.com/group/android-porting/browse_thread/thread/8393f87245699b32#
check to see if you have direct64 in your current kernel headers in bionic
libc.
diff --git a/libc/kernel/common/linux/dirent.h b/libc/kernel/common/
linux/dirent.h
Hi,
The following patch is not necessary. When I did a clean
rebuild, it worked.
09. In file external/icu4c/common/rbbidata.cpp
Error:
target SharedLib: libicuuc (out/target/product/generic/obj/
SHARED_LIBRARIES/libicuuc_intermediates/LINKED/libicuuc.so)
Hi Fadden, Thanks a lot for your reply!! :-) The TI
OMAP3503 which uses a Cortex-A8 ARM core is big endian I think.
When I was porting the bionic libc kernel headers to v2.6.31, I noticed that
the byte order was getting redefined, so I explicitly forced ARM BIG ENDIAN
in three
sorry ,I only know using logcat to Debug some app,and look for some
error information.
but I can't use logcat look for the error which can not go into
desktop.
can you tell me more .
thank you!
On Jul 28, 11:55 am, Anil Sasidharan anil...@gmail.com wrote:
Hi,
Please walk through
Hi,
The error that I get is related to the v2.6.31 bionic/libc/
kernel/common/linux/tcp.h file, line 60
enum {
TCP_FLAG_CWR = __cpu_to_be32(0x0080),
TCP_FLAG_ECE = __cpu_to_be32(0x0040),
TCP_FLAG_URG = __cpu_to_be32(0x0020),
TCP_FLAG_ACK = __cpu_to_be32(0x0010),
23 matches
Mail list logo
