> On Jul 4, 1:02 pm, Sheshu Inguva <skumaring...@gmail.com> wrote:
> > hi i tried with opie and it works occasionally, cant boot all the
> > time. most of the times it hangs. i thought android might be having
> > better package file system...
> > On Jul 3, 11:04 pm, NickDG <nick.del.gra...@gmail.com> wrote:
> > > You can try loading the kernel using cocoboot. It unloads Palm OS
> > > then loads a linux kernel you provide. I don't believe Android has
> > > been tried.
> > > > i got some kernel compiled fortreo650/680. what i want is a file
> > > > system on which i can start my device. anybody tried that with
> > > > android?- Hide quoted text -
FYI, I've successfully compiled a kernel using the sources from
Hack&Dev and Cocobooted it on a Treo 650.
But then I lack the knowledge to integrate the Hack&Dev and Android
sources and compile a working kernel. Tried quite a few different ways
but none worked.
Somehow, I got to "How are you gentlemen" once.
Anyway, I don't have plans to work further on it given the hardware
limits of Treo 650.
Cheers.
On Sep 25, 2:58 pm, NickDG <nick.del.gra...@gmail.com> wrote:
> > > hi i tried with opie and it works occasionally, cant boot all the
> > > time. most of the times it hangs. i thought android might be having
> > > better package file system...
> > > > You can try loading the kernel using cocoboot. It unloads Palm OS
> > > > then loads a linux kernel you provide. I don't believe Android has
> > > > been tried.
> > > > > i got some kernel compiled fortreo650/680. what i want is a file
> > > > > system on which i can start my device. anybody tried that with
> > > > > android?- Hide quoted text -
> FYI, I've successfully compiled a kernel using the sources from
> Hack&Dev and Cocobooted it on aTreo650.
> But then I lack the knowledge to integrate the Hack&Dev and Android
> sources and compile a working kernel. Tried quite a few different ways
> but none worked.
> Somehow, I got to "How are you gentlemen" once.
> Anyway, I don't have plans to work further on it given the hardware
> limits ofTreo650.
> Cheers.
> On Sep 25, 2:58 pm, NickDG <nick.del.gra...@gmail.com> wrote:
> > I am hoping Cocoboot will allow us to boot the android kernel. We
> > will need to compile the kernel for the hardware onTreo.
> > First try should be a very simple kernel just to see if it will boot.
> > Then we can start adding stuff from there. (I am hoping)
> > My issues are getting to the bootloader and flashing the phones.
> > P.S. The 800w will probably be easier to hack them you think. ;-)
> > - Nick
> > On Aug 19, 6:55 am, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > > > hi i tried with opie and it works occasionally, cant boot all the
> > > > time. most of the times it hangs. i thought android might be having
> > > > better package file system...
> > > > > You can try loading the kernel using cocoboot. It unloads Palm OS
> > > > > then loads a linux kernel you provide. I don't believe Android has
> > > > > been tried.
> > > > > > i got some kernel compiled fortreo650/680. what i want is a file
> > > > > > system on which i can start my device. anybody tried that with
> > > > > > android?- Hide quoted text -
> The nice guys over Hack&Dev is working to push upstream their work
> into the mainstream kernel.
> So when it's done, and the complete source of Android is released,
> maybe I will try to do it again.
> (Of course, my preferred way is to download a working kernel and the
> userspace, and use it right away... : )
> Still, I'm doubtful if the 650 can handle it... Newer models are
> better spec-ed but then kernel support is an issue.
> On Sep 26, 11:00 am, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > FYI, I've successfully compiled a kernel using the sources from
> > Hack&Dev and Cocobooted it on aTreo650.
> > But then I lack the knowledge to integrate the Hack&Dev and Android
> > sources and compile a working kernel. Tried quite a few different ways
> > but none worked.
> > Somehow, I got to "How are you gentlemen" once.
> > Anyway, I don't have plans to work further on it given the hardware
> > limits ofTreo650.
> > Cheers.
> > On Sep 25, 2:58 pm, NickDG <nick.del.gra...@gmail.com> wrote:
> > > I am hoping Cocoboot will allow us to boot the android kernel. We
> > > will need to compile the kernel for the hardware onTreo.
> > > First try should be a very simple kernel just to see if it will boot.
> > > Then we can start adding stuff from there. (I am hoping)
> > > My issues are getting to the bootloader and flashing the phones.
> > > P.S. The 800w will probably be easier to hack them you think. ;-)
> > > - Nick
> > > On Aug 19, 6:55 am, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > > > > hi i tried with opie and it works occasionally, cant boot all the
> > > > > time. most of the times it hangs. i thought android might be having
> > > > > better package file system...
> > > > > > You can try loading the kernel using cocoboot. It unloads Palm OS
> > > > > > then loads a linux kernel you provide. I don't believe Android has
> > > > > > been tried.
> > > > > > > i got some kernel compiled fortreo650/680. what i want is a file
> > > > > > > system on which i can start my device. anybody tried that with
> > > > > > > android?- Hide quoted text -
> When is the source being released anyways? Seems like it is taking
> forever.
> I have no problems using my Centro as a test phone if we are playing
> with Cocoboot.
> On Oct 5, 9:47 pm, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > The nice guys over Hack&Dev is working to push upstream their work
> > into the mainstream kernel.
> > So when it's done, and the complete source of Android is released,
> > maybe I will try to do it again.
> > (Of course, my preferred way is to download a working kernel and the
> > userspace, and use it right away... : )
> > Still, I'm doubtful if the 650 can handle it... Newer models are
> > better spec-ed but then kernel support is an issue.
> > On Sep 26, 11:00 am, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > > FYI, I've successfully compiled a kernel using the sources from
> > > Hack&Dev and Cocobooted it on aTreo650.
> > > But then I lack the knowledge to integrate the Hack&Dev and Android
> > > sources and compile a working kernel. Tried quite a few different ways
> > > but none worked.
> > > Somehow, I got to "How are you gentlemen" once.
> > > Anyway, I don't have plans to work further on it given the hardware
> > > limits ofTreo650.
> > > > > > hi i tried with opie and it works occasionally, cant boot all the
> > > > > > time. most of the times it hangs. i thought android might be having
> > > > > > better package file system...
> > > > > > > You can try loading the kernel using cocoboot. It unloads Palm OS
> > > > > > > then loads a linux kernel you provide. I don't believe Android has
> > > > > > > been tried.
> > > > > > > > i got some kernel compiled fortreo650/680. what i want is a file
> > > > > > > > system on which i can start my device. anybody tried that with
> > > > > > > > android?- Hide quoted text -
> When is the source being released anyways? Seems like it is taking
> forever.
> I have no problems using my Centro as a test phone if we are playing
> with Cocoboot.
> On Oct 5, 9:47 pm, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > The nice guys over Hack&Dev is working to push upstream their work
> > into the mainstream kernel.
> > So when it's done, and the complete source of Android is released,
> > maybe I will try to do it again.
> > (Of course, my preferred way is to download a working kernel and the
> > userspace, and use it right away... : )
> > Still, I'm doubtful if the 650 can handle it... Newer models are
> > better spec-ed but then kernel support is an issue.
> > On Sep 26, 11:00 am, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > > FYI, I've successfully compiled a kernel using the sources from
> > > Hack&Dev and Cocobooted it on aTreo650.
> > > But then I lack the knowledge to integrate the Hack&Dev and Android
> > > sources and compile a working kernel. Tried quite a few different ways
> > > but none worked.
> > > Somehow, I got to "How are you gentlemen" once.
> > > Anyway, I don't have plans to work further on it given the hardware
> > > limits ofTreo650.
> > > > > > hi i tried with opie and it works occasionally, cant boot all the
> > > > > > time. most of the times it hangs. i thought android might be having
> > > > > > better package file system...
> > > > > > > You can try loading the kernel using cocoboot. It unloads Palm OS
> > > > > > > then loads a linux kernel you provide. I don't believe Android has
> > > > > > > been tried.
> > > > > > > > i got some kernel compiled fortreo650/680. what i want is a file
> > > > > > > > system on which i can start my device. anybody tried that with
> > > > > > > > android?- Hide quoted text -
> When is the source being released anyways? Seems like it is taking
> forever.
> I have no problems using my Centro as a test phone if we are playing
> with Cocoboot.
> On Oct 5, 9:47 pm, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > The nice guys over Hack&Dev is working to push upstream their work
> > into the mainstream kernel.
> > So when it's done, and the complete source of Android is released,
> > maybe I will try to do it again.
> > (Of course, my preferred way is to download a working kernel and the
> > userspace, and use it right away... : )
> > Still, I'm doubtful if the 650 can handle it... Newer models are
> > better spec-ed but then kernel support is an issue.
> > On Sep 26, 11:00 am, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > > FYI, I've successfully compiled a kernel using the sources from
> > > Hack&Dev and Cocobooted it on aTreo650.
> > > But then I lack the knowledge to integrate the Hack&Dev and Android
> > > sources and compile a working kernel. Tried quite a few different ways
> > > but none worked.
> > > Somehow, I got to "How are you gentlemen" once.
> > > Anyway, I don't have plans to work further on it given the hardware
> > > limits ofTreo650.
> > > > > > hi i tried with opie and it works occasionally, cant boot all the
> > > > > > time. most of the times it hangs. i thought android might be having
> > > > > > better package file system...
> > > > > > > You can try loading the kernel using cocoboot. It unloads Palm OS
> > > > > > > then loads a linux kernel you provide. I don't believe Android has
> > > > > > > been tried.
> > > > > > > > i got some kernel compiled fortreo650/680. what i want is a file
> > > > > > > > system on which i can start my device. anybody tried that with
> > > > > > > > android?- Hide quoted text -
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
> 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 <nowel...@gmail.com> wrote:
> Not really sure. We aren't at that level yet! ;)
> One step at a time.
> On Oct 23, 9:54 pm, 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?
> I believe a good starting point would be to compile a Linux 2.6.23
> kernel for the Treo's ARM architecture.
> From what I am reading, Android will work on any 2.6.23 kernel.
> We should be able to move quickly from there. :)
> - Nick
> On Oct 24, 1:15 am, NickDG <nick.del.gra...@gmail.com> wrote:
> > Not really sure. We aren't at that level yet! ;)
> > One step at a time.
> > On Oct 23, 9:54 pm, 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?
> The recommended tree for 650 over Hack&Dev is 2.6.27 (http://
> git.hackndev.com/?p=linux-2.6;a=summary). Not sure about the other
> devices.
> Anyway, after reading the "releases features" (http://
> source.android.com/release-features), my hope is greatly dash... : )
> "The platform requires a minimum of 128 MB of RAM and 256 MB of Flash
> memory."
> On Oct 24, 4:19 pm, NickDG <nick.del.gra...@gmail.com> wrote:
> > I believe a good starting point would be to compile a Linux 2.6.23
> > kernel for the Treo's ARM architecture.
> > From what I am reading, Android will work on any 2.6.23 kernel.
> > We should be able to move quickly from there. :)
> > - Nick
> > On Oct 24, 1:15 am, NickDG <nick.del.gra...@gmail.com> wrote:
> > > Not really sure. We aren't at that level yet! ;)
> > > One step at a time.
> > > On Oct 23, 9:54 pm, 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?
> I still have hope! 64MB/64MB should be enough! (650 probably won't
> cut it) :(
> You mentioned in a previous post you booted your Treo to Linux with
> Cocoboot. What Linux kernel did you use?
> Thanks
> - Nick
> On Oct 24, 8:46 am, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > Android is based on 2.6.25.
> > The recommended tree for 650 over Hack&Dev is 2.6.27 (http://
> > git.hackndev.com/?p=linux-2.6;a=summary). Not sure about the other
> > devices.
> > Anyway, after reading the "releases features" (http://
> > source.android.com/release-features), my hope is greatly dash... : )
> > "The platform requires a minimum of 128 MB of RAM and 256 MB of Flash
> > memory."
> > On Oct 24, 4:19 pm, NickDG <nick.del.gra...@gmail.com> wrote:
> > > I believe a good starting point would be to compile a Linux 2.6.23
> > > kernel for the Treo's ARM architecture.
> > > From what I am reading, Android will work on any 2.6.23 kernel.
> > > We should be able to move quickly from there. :)
> > > - Nick
> > > On Oct 24, 1:15 am, NickDG <nick.del.gra...@gmail.com> wrote:
> > > > Not really sure. We aren't at that level yet! ;)
> > > > One step at a time.
> > > > On Oct 23, 9:54 pm, 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?
In case you're interested, you may get my zImage and cocoboot.conf
from http://ifile.it/2msu7on
FYI, I formatted the SD card into 2 partitions - The first was a FAT16
for the kernel and cocoboot.conf. The second was an ext2 containing
the Android file system downloaded from somewhere.
In case you would like to do it yourself, you may like to setup the
environment for compiling the kernel (i.e. a Linux distro and ARM
toolchains...), and get a kernel (without the Android patches)
successfully compiled and booted on your device first.
Cheers and have a nice weekend!
On Oct 25, 3:14 am, NickDG <nick.del.gra...@gmail.com> wrote:
> I still have hope! 64MB/64MB should be enough! (650 probably won't
> cut it) :(
> You mentioned in a previous post you booted your Treo to Linux with
> Cocoboot. What Linux kernel did you use?
> Thanks
> - Nick
> On Oct 24, 8:46 am, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > Android is based on 2.6.25.
> > The recommended tree for 650 over Hack&Dev is 2.6.27 (http://
> > git.hackndev.com/?p=linux-2.6;a=summary). Not sure about the other
> > devices.
> > Anyway, after reading the "releases features" (http://
> > source.android.com/release-features), my hope is greatly dash... : )
> > "The platform requires a minimum of 128 MB of RAM and 256 MB of Flash
> > memory."
> > On Oct 24, 4:19 pm, NickDG <nick.del.gra...@gmail.com> wrote:
> > > I believe a good starting point would be to compile a Linux 2.6.23
> > > kernel for the Treo's ARM architecture.
> > > From what I am reading, Android will work on any 2.6.23 kernel.
> > > We should be able to move quickly from there. :)
> > > - Nick
> > > On Oct 24, 1:15 am, NickDG <nick.del.gra...@gmail.com> wrote:
> > > > Not really sure. We aren't at that level yet! ;)
> > > > One step at a time.
> > > > On Oct 23, 9:54 pm, 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?
> In case you're interested, you may get my zImage and cocoboot.conf
> fromhttp://ifile.it/2msu7on
> FYI, I formatted the SD card into 2 partitions - The first was a FAT16
> for the kernel and cocoboot.conf. The second was an ext2 containing
> the Android file system downloaded from somewhere.
> In case you would like to do it yourself, you may like to setup the
> environment for compiling the kernel (i.e. a Linux distro and ARM
> toolchains...), and get a kernel (without the Android patches)
> successfully compiled and booted on your device first.
> Cheers and have a nice weekend!
> On Oct 25, 3:14 am, NickDG <nick.del.gra...@gmail.com> wrote:
> > I still have hope! 64MB/64MB should be enough! (650 probably won't
> > cut it) :(
> > You mentioned in a previous post you booted your Treo to Linux with
> > Cocoboot. What Linux kernel did you use?
> > Thanks
> > - Nick
> > On Oct 24, 8:46 am, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > > Android is based on 2.6.25.
> > > The recommended tree for 650 over Hack&Dev is 2.6.27 (http://
> > > git.hackndev.com/?p=linux-2.6;a=summary). Not sure about the other
> > > devices.
> > > Anyway, after reading the "releases features" (http://
> > > source.android.com/release-features), my hope is greatly dash... : )
> > > "The platform requires a minimum of 128 MB of RAM and 256 MB of Flash
> > > memory."
> > > On Oct 24, 4:19 pm, NickDG <nick.del.gra...@gmail.com> wrote:
> > > > I believe a good starting point would be to compile a Linux 2.6.23
> > > > kernel for the Treo's ARM architecture.
> > > > From what I am reading, Android will work on any 2.6.23 kernel.
> > > > We should be able to move quickly from there. :)
> > > > - Nick
> > > > On Oct 24, 1:15 am, NickDG <nick.del.gra...@gmail.com> wrote:
> > > > > Not really sure. We aren't at that level yet! ;)
> > > > > One step at a time.
> > > > > On Oct 23, 9:54 pm, 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?
> > > > > > On Tue, Oct 21, 2008 at 1:04 PM, nowell29 <nowel...@gmail.com> 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.
> > In case you're interested, you may get my zImage and cocoboot.conf
> > fromhttp://ifile.it/2msu7on
> > FYI, I formatted the SD card into 2 partitions - The first was a FAT16
> > for the kernel and cocoboot.conf. The second was an ext2 containing
> > the Android file system downloaded from somewhere.
> > In case you would like to do it yourself, you may like to setup the
> > environment for compiling the kernel (i.e. a Linux distro and ARM
> > toolchains...), and get a kernel (without the Android patches)
> > successfully compiled and booted on your device first.
> > Cheers and have a nice weekend!
> > On Oct 25, 3:14 am, NickDG <nick.del.gra...@gmail.com> wrote:
> > > I still have hope! 64MB/64MB should be enough! (650 probably won't
> > > cut it) :(
> > > You mentioned in a previous post you booted your Treo to Linux with
> > > Cocoboot. What Linux kernel did you use?
> > > Thanks
> > > - Nick
> > > On Oct 24, 8:46 am, Lo Yuk Fai <loyuk...@gmail.com> wrote:
> > > > Android is based on 2.6.25.
> > > > The recommended tree for 650 over Hack&Dev is 2.6.27 (http://
> > > > git.hackndev.com/?p=linux-2.6;a=summary). Not sure about the other
> > > > devices.
> > > > Anyway, after reading the "releases features" (http://
> > > > source.android.com/release-features), my hope is greatly dash... : )
> > > > "The platform requires a minimum of 128 MB of RAM and 256 MB of Flash
> > > > memory."
> > > > On Oct 24, 4:19 pm, NickDG <nick.del.gra...@gmail.com> wrote:
> > > > > I believe a good starting point would be to compile a Linux 2.6.23
> > > > > kernel for the Treo's ARM architecture.
> > > > > From what I am reading, Android will work on any 2.6.23 kernel.
> > > > > We should be able to move quickly from there. :)
> > > > > - Nick
> > > > > On Oct 24, 1:15 am, NickDG <nick.del.gra...@gmail.com> wrote:
> > > > > > Not really sure. We aren't at that level yet! ;)
> > > > > > One step at a time.
> > > > > > On Oct 23, 9:54 pm, 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?
> > > > > > > On Tue, Oct 21, 2008 at 1:04 PM, nowell29 <nowel...@gmail.com> 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.
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:
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
> On Tue, Oct 21, 2008 at 1:04 PM, nowell29 <nowel...@gmail.com> 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" <thiago.bec...@gmail.com>
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:
> 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?
> 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" <thiago.bec...@gmail.com>
> 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:
> > 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?
> hmmm...I'll be watching this thread closely for progress on a centro
> port. Good work fellas
> On Oct 25, 6:11 pm, NickDG <nick.del.gra...@gmail.com> 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" <thiago.bec...@gmail.com>
> > 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:
> > > 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?
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 <loyuk...@gmail.com> 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 <Nadeem.Mun...@gmail.com> 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 <nick.del.gra...@gmail.com> 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" <thiago.bec...@gmail.com>
> > > 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:
> > > > 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?
