[okl4-developer] porting OKL4 to a different architecture

[Gabi Voiculescu]

Hi.


--- On Tue, 11/3/09, Andrei Voinescu <voinescu.andrei at gmail.com> wrote:

From: Andrei Voinescu <voinescu.andrei at gmail.com>
Subject: [okl4-developer] porting OKL4 to a different architecture
To: developer at okl4.org
Date: Tuesday, November 3, 2009, 2:10 PM

Hi,

We (two colleagues and myself) would be interested in porting okl4 to the avr32 architecture. I would like to ask you a couple of questions:


1) Is there any license difference between okl4-3.0 and 2.1?


2) What steps should we take to port? First the arch/avr32 then go through the SoC porting process?
Yes.

3) What would be the minimal subset of features needed to test the build for a different architecture?
arch/avr32platform/platformavr32
drivers/v2serial_on_platformavr32
drivers/v2timer_on_platformavr32

You need the first three functional for ktest unit test suite.
You need the first four functional for ctest.

So hardware requirements are: 2 separate timers, at least one serial port.
Thanks,




Andrei




-----Inline Attachment Follows-----

_______________________________________________
Developer mailing list
Developer at okl4.org
https://lists.okl4.org/mailman/listinfo/developer



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20091103/66c1e348/attachment.htm