[okl4-developer] OKL4 3.0 for HTC Dream ("Google G1") and the Android emulator

Nicholas FitzRoy-Dale nfd at cse.unsw.edu.au
Sun Mar 15 14:09:54 EST 2009


On 15/03/2009, at 1:45 PM, Guanghui, Cheng wrote:

> 	Thanks for your post first.
> 	It seems there is an error in this tarball when i compile okl4 for  
> androidsim
> as following:
> platform/goldfish/pistachio/src/interrupt.c:197: error: conflicting  
> types
> for 'soc_ack_interrupt'

Thanks very much for pointing this out. I'll update the tarball  
shortly. I must have broken the emulator port while working on the  
Dream port.

> 	The second problem is about cross-compiler. Before i always use the
> cross-compiler arm-none-linux-gnueabi-gcc and arm-linux-gcc  
> suggested in the
> document in the official website. But in this tarball it seems to use
> arm-elf-eabi-gcc. Something is changed?

Your compiler should be fine. I had to compile my own toolchain  
because I use a Mac, and doing anything with GNU libc on a Mac is very  
painful. :-)

> 	The third question is about the template when porting. I read your  
> code and
> find the template you used is the platform "pxa". But actually the  
> templte i
> used is the platform "versatile". I thought versatile and goldfish  
> have the
> same CPU type "arm926ejs".  I think that is the mistake when i  
> ported. Can
> you explain why you choose the platform "pxa" not "versatile".

You're right about the chip type. The goldfish machine description  
(platform/goldfish/tools/machines.py) uses the arm926ejs chip, so as  
long as your port does the same you should be fine. I just used pxa  
because when I was doing the port (which was a while ago) the pxa  
platform was a little more up-to-date and easier to read. None of the  
actual code from the PXA port gets used anywhere else, so machines.py  
should be the only important file.

Good luck!

Nicholas




More information about the Developer mailing list