Can't we just work off the kernel being used over at Hack&Dev? I was just reading they got the Centro and 700p booting using the 680 kernel.
We can build upon this kernel to add support for the various hardware. If the display and keyboard are working in the current release, it may be enough to start Android. Someone please correct me if I am wrong, but if we get a working Linux kernel, we should be able to use an already-ARM-compiled Android system, living on an ext3fs partition. (SDcard) - Nick On Oct 27, 12:28 pm, Lo Yuk Fai <[EMAIL PROTECTED]> wrote: > What I have done was just downloading some codes, typed in some > commands and so. > > I think we need someone knowledgeable in hacking the kernel to step in > in order to get it goes further... : ) > > Cheers! > > On Oct 26, 11:39 am, Stillmatic <[EMAIL PROTECTED]> wrote: > > > hmmm...I'll be watching this thread closely for progress on a centro > > port. Good work fellas > > > On Oct 25, 6:11 pm, NickDG <[EMAIL PROTECTED]> wrote: > > > > 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 > > > the same boat with the Libraries? > > > > 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 > > > the file system, because I haven't created a file system on the second > > > parition yet. (I am only using 1 partition) > > > > I am trying to get a kernel booting on newer Treo devices with > > > Cocoboot. Stay tuned... > > > > Cheers! > > > > - Nick > > > > On Oct 24, 10:02 am, "Thiago Rafael Becker" <[EMAIL PROTECTED]> > > > wrote: > > > > > 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 Beckerhttp://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 -~----------~----~----~----~------~----~------~--~---
