Hi Deva,
Thanks for that post. I am using AM3517EVM from logic PD having AM3517
processor http://focus.ti.com/docs/prod/folders/print/am3517.html
but OMAP3 EVM has OMAP3530 processor. Is the Android port for rowboat
proj directly compatible for AM3517 ?
Regards,
chinmay
On Feb 24, 7:08 pm, Deva
Are you sure that the port there will work on AM3517 platform because
both OMAP3EVM and AM3517 platform are different.
On Feb 24, 7:08 pm, Deva R r.deva...@gmail.com wrote:
i guess you are using EVM board.. Android ports are readily available for
EVM boards,,
rowboat proj
Hi
can anyone let me know proper steps to be taken for integration on h/w
accelerators ( graphic ) for android 1.6 on x86 platform, so that i
can use my vendor provided shared objects for EGL and OpenGLES 1.1
instead of the already available libraries and the libagl.so.
Any information related
Does the OMAP3 EVM consists of the TI AM3517 processor. Are you sure
can people use the Android ports for OMAP3 EVM on AM3517?
On Feb 24, 7:08 pm, Deva R r.deva...@gmail.com wrote:
i guess you are using EVM board.. Android ports are readily available for
EVM boards,,
rowboat proj
That is correct.
On Feb 24, 1:44 am, arindam das das.ar...@gmail.com wrote:
Hi Uander ,
I guess ur doing it correctly.While running the test
cases already provided by the PVcore,one can only see the logs and not the
output on the screen or the speaker.
This is what my
To list..
-- Ashwin
-- Forwarded message --
From: Ashwin Bihari abih...@gmail.com
Date: Thu, Feb 25, 2010 at 9:30 AM
Subject: Re: [android-porting] Re: Android porting on AM3517
To: chinmay.chow...@gmail.com
Rowboat doesn't have support for the AM3517 EVM yet..you will need
sorry, those ports are for EVM with OMAP3.
AM3517 is a spin of OMAP3, and is present in its own EVM..
you need this port available
http://www.linuxhq.com/kernel/v2.6/32-git15/arch/arm/mach-omap2/board-am3517evm.c
On Thu, Feb 25, 2010 at 3:43 PM, Murugaprabu Marimuthu
murugapra...@gmail.com
As far ar I know, the system images that are provided with the SDK are built
in the same way than the ones that run on retail Dream/G1 and Magic/MyTouch
devices.
In other words, they are not tuned specifically for the emulator (but they
contain emulator-specific code that is not part of the system
Did you check your system/bin to see if wpa_supplicant was present?
Here is what's in my BoardConfig.mk in order to build wpa supplicant.
# Wifi related defines
BOARD_WPA_SUPPLICANT_DRIVER := WEXT
BOARD_WPA_SUPPLICANT_PRIVATE_LIB :=
On Feb 23, 3:56 am, Gaan gaan...@gmail.com wrote:
Hi
Hi all,
I am trying to understand the different components of Android's
display system and how they work together. I have been sifting
through the source, but I still have a few fundamental questions.
Here is my current understanding of a couple of these components:
SurfaceFlinger: It composes
Are you sure that this functionality is supported by your Kernel and
Target hardware?
Regards,
Sreekanth
On Feb 24, 8:16 pm, Ashwin Bihari abih...@gmail.com wrote:
I've got a custom board designed around the OMAP3530 and we have a
power button the device that we want to use to cause Android to
I guess you intend to power off the device when you hit the power button
right?
First, the keycode as you mentioned should map Android power key. Secondly,
you should
have proper hook in baseport level for pm_power_off() for DEVICE OFF.
-Girish
On Wed, Feb 24, 2010 at 9:16 AM, Ashwin Bihari
Thanks.
So you mean to say that when i compile a native code using the
prebuilt toolchain of Android for emulator,
the ARM instructions generated is in no way limited by some
limitations of the emulator(if any).
ajay
On Feb 26, 12:55 am, David Turner di...@android.com wrote:
As far ar I know,
13 matches
Mail list logo
