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 <[EMAIL PROTECTED]> 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 > > On Tue, Oct 21, 2008 at 1:04 PM, nowell29 <[EMAIL PROTECTED]> wrote: >> >> the source has now been released. >> http://www.linuxdevices.com/news/NS9433817554.html?kc=rss >> I have a treo 680 that I would gladly experiment with/on. Thanks for >> all the hard work everybody. >> >> > >> > > > > -- Thiago Rafael Becker http://www.monstros.org/trbecker --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to android-internals@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
