[Tinyos-devel] Request for comments: TEP-108

[Matt Welsh]

Folks,

Thanks for all of the comments and discussion on TEP-108. Please keep  
the comments coming.
I am going to roll all of these together into comments back to Kevin  
when we are done with the
shepherding period.

Thanks!
Matt


On Nov 6, 2006, at 12:35 PM, Miguel Freitas wrote:

> On 11/6/06, Kevin Klues <klueska at gmail.com> wrote:
>> These aren't so much comments on the contents of the TEP, but rather
>> on how to use the features it presents.  Implementations of Arbiters
>> according to the TEP exist in the development branch of cvs on
>> sourceforge, but not on the main branch.
>
> ok, as i said, i'm a newcomer... i wasn't sure if TEP documented how
> things worked or how they are supposed to work ;-)
>
> i'm using cvs already, i will also check this development branch.
>
>> One thing to note, however, is that using the ResourceRequested
>> interface alone in order to decide when to release a resource is
>> discouraged for devices that wish to use the power management  
>> features
>> available with T2.  If clients only release resources based on a
>> ResourceRequested event, then the resource will never have the chance
>> to go idle and any power managers wired to the ResoruceController
>> interface provided by the resource's arbiter will not be able to  
>> power
>> it on/off automatically.
>
> agreed.
>
> yesterday i wrote a first version of the mts300's photo and temp
> components and i tried to go safe: resource is acquired 10ms before
> acquisition (to allow sensors to power up) and released as soon as AD
> conversion completes.
>
>> I think what is typically done is that the SIDs read interface is
>> implemented using the ADC HIL Read interface and the SIDs ReadStream
>> interface is implemented using the ADC HIL ReadStream interface so
>> that you don't have to worry about the details of dealing with the
>> Resource yourself unless it is specifically required for your
>> implementation (that's why the ReadNow interface exists).  The
>> sensorboard implementation thus takes care of configuring the ADC
>> correctly and then calling its respective Read and ReadStream
>> implementations....
>
> i'm not intimate with all these interfaces... i guess i still have a
> lot of TEPs and code to read!
>
> Miguel
> _______________________________________________
> Tinyos-devel mailing list
> Tinyos-devel at Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/ 
> tinyos-devel