[Tinyos-help] Re: [Tinyos-devel] CTP + LPL

Philip Levis pal at cs.stanford.edu
Sun Feb 10 15:46:58 PST 2008


On Feb 10, 2008, at 2:52 PM, John Griessen wrote:

> Matt Welsh wrote:
>
>> As I understand it, the point was that you're supposed to get  
>> things approved in TEPs *first* (so everyone agrees on the  
>> interfaces and functionality) and *then* go write the code.  
>> Usually we do it the other way around and the TEP approval ends up  
>> being a rubber stamp on whatever happens to be in the code.
>
>> It is clear that there is a tension between wanting to innovate  
>> rapidly on one hand and maintain a formal procedure for vetting of  
>> interfaces and code on the other. I'm not sure how to resolve this.
>
>
>>> On Feb 8, 2008 12:45 PM, Vlado Handziski <handzisk at tkn.tu- 
>>> berlin.de> wrote:
>  the public interfaces
>>>> at both
>>>> the HAL and the HIL level have to be documented and accepted  
>>>> through the TEP
>>>> process before becoming part of the core.
>
> So, is a DAC setting module a candidate for a TEP?  I think it is a  
> natural
> for sensor networks, since it corresponds to sensor excitation  
> source for a sensor
> mostly done in code with analog resources (spare op amps,  
> comparators), increasingly found on microcontrollers,
> plus a handful of passive parts.

It is. TEPs have to have an associated/sponsoring working group, but  
their authors need not need to be a member of the WG.

Phil




More information about the Tinyos-devel mailing list