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

[John Griessen]

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.

John Griessen

-- 
Ecosensory   Austin TX
tinyOS devel on:  ubuntu Linux;   tinyOS v2.0.2;   telosb ecosens1