Originally Posted by devslashnull

The next things to do are (well, as I see it):

1) get the onscreen keyboard working again
2) get the sd card driver to work properly
3) boot the kernel with haret, but with a rootfs mounted on the external sd card
4) get some sort of way working to get kernel debug messages (the VOGUE kernel has a way to log kernel messages to ram, and dump the ram after a soft-reset from Windows Mob.).

Darn, I was working with wrong sources. I checked out the ones you mentioned - 2.6.25 from git.android.com with 3 patches from szsoftware. I will try to get onscreen keyboard working again.

Nice progress I hope I can find some spair time to do something myself, but I haven't seen a working zImage in a while, so this really is a good start

The first thing to do is to check your tree against mine and make sure there are no differences at all in the sd driver, dma and irq code. if there aren't, then find a way to make it fall over reliably and try changing things like the maximum block size and block count to see if that makes a difference. If this all fails then the driver has a PIO mode, wince uses pio rather than dma. PIO mode has not been enabled since an early driver but i think the very latest (in the android open source tree) also uses it, so look at that too. It's possible that the gpios need to be configured differently, try tracing the alt_config address.

This looks like the next thing to do (really don't know what he is talking about, hope someone does... and can clear things up )

The logs from the htc-linux irc room show a lot of activity. Looks like we have a "booting" 1.0 android with some errors is that correct?

Also can someone post the entire lot of files being used to do this please?

Theres a whole load of different files posted on the other thread and it would be good if we could all see the same thing - at least the eager testers could report back what their experiences are, you never know what breakthrough you may get from having it run on different setups.

I also want to update the first post with these files so that we can point everyone who comes on here wanting to get involved to the most current file set.

Congratulations to the team that it`s developing it, and good luck!.I`m really excited, I`m quite of a linuz fan so you can get an idea

Originally Posted by bally3

The logs from the htc-linux irc room show a lot of activity. Looks like we have a "booting" 1.0 android with some errors is that correct?

Also can someone post the entire lot of files being used to do this please?

Theres a whole load of different files posted on the other thread and it would be good if we could all see the same thing - at least the eager testers could report back what their experiences are, you never know what breakthrough you may get from having it run on different setups.

I also want to update the first post with these files so that we can point everyone who comes on here wanting to get involved to the most current file set.

great idea Btw, isn't it an idea to donate DZO a Polaris (if he is willing to port linux to it), think there are cheap Polaris phones on eBay... Is a quick solution for our problem, he has all the knowledge, and was willing to do the same for the Kaiser.

Last night, rolk on irc helped me get linux "running" on my device at root level and a prompt using Angstrom. (Thanks Rolk! )

I enquired how to get the GUI running and was told that, this could be done by typing startX. This didnt work and I was told that this could be found in the initrd file but Angstrom doesnt have startX as far as its known. I left it at that deciding to have another go today.

This morning I read the logs again, and a user called glyph who was trying to do the same as myself - get the system up and running to see whats been done and what needs doing, asked a simple question after having followed the instructions and got to the prompt as myself - "How do I get android working on the device?" and got a confusing response.

I assume, like myself that Glyph is still confused as to what do next.

And here lies the problem. Its an endemic problem with linux and its multitude of incarnations - linux power users vs the the "NOOB".

What THE END-USER on here wants to do is to get an Android version of Linux working on their phones.

What the power users want to do is to create a whole new Linux version for these devices.

Theres nothing wrong with either endeavours and I understand the wish of linux users to get away from Googles close-sourcing and its control issues and secret patches but we seem to be working on multiple projects at the same time.

I personally would like to see DZO's vogue version working on my Polaris - and I think the majority of the users here would like to see the same.

I dont understand why we are using Angstrom over the other initrd if it does not contain the android GUI, If I understand correctly, DZO was using 1.0 android and the initrd file from what I see in the download from his site. I would like to know what needs to be done to his setup to make it work with ours.

I hope someone can explain who's working on what project and maybe we should separate the two endeavours if that is indeed what is happening.

Whilst creating a linux from scratch for these devices is a noble endeavour, the sheer scale of this task is something which I think should be left for a dedicated thread with its own project name.

That what i was saying we should create new topic, there is the kernel first, and after that we can run many distrib on polaris. the kernel is indepedant from distrib. That's an important point.

Angstrom is just a simple distrib without X but you can test gprs and different things but all in commande line

DZO use the 1.0 SDK files on a SD format in ext3 and he ahs a specific version of haret.
With polaris we have problem because some code to boot aren't the same as the vogue so we can't use DZO's vigue files like that.

That why DZO ask a kaiser or a Polaris to see what's cause probleme and repair that to release a version for our device.

As you said in this thread people really want to see Android running, not another distrib.That why i suggested to make 2 thread but its complicated to read multi-thread after. (we already have lot information on Kaiser +vogue+ polaris threads)

Originally Posted by imfloflo

DZO use the 1.0 SDK files on a SD format in ext3 and he ahs a specific version of haret.
With polaris we have problem because some code to boot aren't the same as the vogue so we can't use DZO's vigue files like that.

Cant we fix the problem with the code or is that not within the capabilities of the devs on this thread? Sending DZO a polaris doesnt seem to be much of an option to me.

I think it's require lot of skills in basic dev, maybe ASM, or like that.

I think we should wait he receive his kaiser from another member of XDA and see if we can use this.

After that if no solution found we must send him a Polaris

good news here

Originally Posted by dzo

Hi,
Good news is that I'm being sent a fully working Kaiser by an xda member (who wants to remain anonymous). I'm going away until just after xmas so won't be able to do anything until I get back but then I'll be spending lots of time with it.

Thanks anonymous Kaiser donor.