Great news about the porting. The 650-Centro all have armv5 cpus.
The Treo Pro and Treo 800w use armv6 cpus. I am guessing we are in
I found my 650. Using the kernel Lo Yuk Fai provided along with
Cocoboot, I was able boot. I get a kernel panic when it tries to load
parition yet. (I am only using 1 partition)
Cocoboot. Stay tuned...
> The dalvik source code is available, and there are less than a
> handfull of files that will need to be ported (as I looked so far).
> For a device with armv5, or with the same instruction mnemonics and
> semantics, no port effort will be needed.
> For other platforms, one should take a look on all of the .S files
> (277 files), and three files that have inline asm:
>
> ./vm/mterp/out/InterpC-armv5.c
> ./vm/mterp/armv5/debug.c
> ./vm/Atomic.h
>
> The first two have only declarations of register for certain variables.
>
> Some collateral changes will be needed for platforms that are not
> RISC-like (with fewer registers, like Intel's Atom).
>
> But I have a question: any effort into porting dalvik to non-embedded
> non-RISC linux?
>
>
>
> On Fri, Oct 24, 2008 at 2:54 AM, windstorm <
likunarmstr...@gmail.com> wrote:
>
> > I have a one quick question
>
> > How do you guys deal with Dalvik virtual machine? If you just port the
> > kernel image to the real device, without porting the dalvik which
> > seems to be compiled by non-standard-libc, you should not be able to
> > run any application wrote by yourself, right?
>
> > ----------------------------------------------------------------------------------
> > Yours Sincerely
> > Kun
>