[Tinyos-devel] Request for comments: TEP107

[Martin Leopold]

Hi All.
After reading the tep I have a question and a couple of comments:

 * The references are not referred and linked to the way other TEP's do
it: (ex. [_tep108]). Either as [1] or with no link:
 section 4 "TEP 2", 4.1 "TEP  106", 4.1 "TEP 108", 4.1 "TEP 102"

 * The last 2 paragraphs of Section 4.2 are not related to interrupts
and would come more natural moved forward (say 4.1 or in a separate
section).

 * When reading section 4 it is unclear to me where to wire
initialisation rutines for simple peripheral hardware components such as
a UART, i2c, timer, etc.. Should it go in PlatformC? Is it wired to
SoftwareInit?

The TEP says "Components whose initialization does not directly depend
on hardware resources SHOULD wire to MainC.SoftwareInit" if I reverse
this it sayw: components that do depend on hardware should go in
PlatformC.

This is probably not the intention, but that is what I read (this would
imply that all the HW-component-initializers are always included).

I tried to look through the code to find some clues, but there seems to
be a bunch of different approaches:

intelmote2
Seems to create a hierarchy of "Init" interfaces in PlatformP and the hw
components wire to a specific interface (i2c, dma, timer, ...). I can't
seem to figure out where the UART init rutine is wired (up to the
application?)

Mica*
 PlatformP seem to measure the clock and call MoteInit
 The uart (from atm128) is wired to SoftwareInit
 I cant seem to find out where spi, i2c init rutines go

Telosa (is that part of release?)
 In PlatformP it seems that the Leds, Clock and MoteInit are called.
 MoteInit call a bunch of very 1.x like macro to setup pin directions

EyesIFX
 Seems to init LEDs and clock in PlatformP others Uart (and more) wire
to SoftwareInit
 

On Mon, 2006-10-23 at 10:55 -0700, David Moss wrote:
> TinyOS Developers:
>  
> We're looking for volunteers to read over the TEP107 draft and provide
> comments and suggestions.  This TEP describes the TinyOS 2.x Boot
> Sequence, including the limitations of the TinyOS 1.x boot process
> and improvements made in TinyOS 2.x.
>  
> If you have time to read over TEP107 and send me your input, I will be
> working with the author to revise the proposal as needed.  After this
> process is complete, the TEP107 proposal will be moving to a final
> draft, so it is important to hear your feedback now.
>  
> Please send critiques to tinyos-devel at millennium.berkeley.edu
>  
> Thanks,
> -David Moss
>  
>  
> TEP107:
>  http://tinyos.cvs.sourceforge.net/*checkout*/tinyos/tinyos-2.x/doc/html/tep107.html
> _______________________________________________
> Tinyos-devel mailing list
> Tinyos-devel at Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
-- 
Regards Martin Leopold.
Dept. of Computer Science, University of Copenhagen
http://www.diku.dk/~leopold