RFC: RTOS for Calypso

246tnt at gmail.com 246tnt at gmail.com
Sat May 14 20:41:59 UTC 2011


> So unless anyone raises major objections, I think we should move ahead
> with Nuttx. Who is interested in working on the calypso port?

I'd definitely like to be involved in that, especially for the GSM specific  
part and
L1 integration and possibly trying to define more abstract interface for it  
(so that we can switch from calypso to MTK. The current common code makes  
calls from common code to calypso specific stuff directly).

I'm off until next week but after that I'll definitely look into it.

Some things from the top of my head that needs to be taken care of from the  
get go (to be on solid ground):

- Platform (mtk / calypso / qemu?) and board support. Possibly even variant  
(US / EU versions)
- Configuration options (TX enable / debug mode / ... )
- For each type of device (spi / i2c / keyboard / ...), define a  
clear 'Driver API' that each specific driver
- As you said, memory allocator :)

(note that some/many of those may be taken care of by nuttx itself)

> Meanwhile we will figure out how it would be
> possibel to keep the gsm related 'application' code out-of-tree from
> the nuttx code base.

Any idea how to do that yet ?

Essentially the GSM part is three things :

- A collection of drivers for the hw part
- A FIQ handler (the only one)
- A background task that communicates with serial. (altough currently it's  
all handled in IRQ and that's bad)

I'm kind of in favor of progressively recopying all the code we have in a  
new directory and clean it up as we go. (so we keep the currently working  
L1 in the current dir and just progressively import functionality).
This way we can at each addition take care of what we did wrong the first  
time around.

(And I'd definitely like to be involved in that process).


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110514/3c26544d/attachment.html>

More information about the baseband-devel mailing list