[Tinyos Core WG] Re: non-TEP code

[Joe Polastre]

(1) The teleconferences are not at a time that meets my schedule

(2) Notify and Get were accepted by Gil and I, but I still see no
reason why it is "TelosUserButtonC" instead of "UserButtonC" which can
exist on any platform.  It sounds to me like you wish that nesC has
namespaces but since it does not, you are artificially imposing naming
constructs on the components.

(3) Button is the least important of all concepts, yet it seems like
the only thing that generates discussion in this community (which
exponentially slows down the progress).  It appears that simple things
that are understood are discussed in excruciating and unnecessary
detail (buttons--although phil, buttons are simply buttons and not
touch sensitive devices!, LEDs--did we really have a 60 message thread
about LEDs?, and schedulers--has anyone really ever used a TinyOS
scheduler that is not FCFS?).  It would be great to get into the more
pressing issues of using WSNs that are ways beyond these simple
constructs.

-Joe

On 1/29/07, Philip Levis <pal at cs.stanford.edu> wrote:
> On Jan 29, 2007, at 11:17 PM, Joe Polastre wrote:
>
> > On November 27 2006, two months ago, I wrote an email asking how to
> > get a button driver committed to T2.
>
> If I recall correctly, the answer was "write a component which
> follows the Source and Sink Independent Drivers TEP (114)."[1] It was
> on the agenda for the December 6 call but we didn't get to it because
> you didn't call in (and so it fell in priority in discussion).[2] It
> then came up again on December 20, but again, no-one on the call was
> that interested in discussing it, in contrast to a possible bug in
> Alarm on the MSP430, source addressing in base stations, and
> microcontroller management.[3] As you're in the WG, you are of course
> welcome to call in.
>
> If you'd like to resuscitate the issue, then please do.
>
> Phil
>
> [1] http://mail.millennium.berkeley.edu/pipermail/tinyos-2.0wg/2006-
> December/002731.html
> [2] http://tinyos.stanford.edu:8000/TinyOS_2.x_WG/12.06.2006
> [3] http://tinyos.stanford.edu:8000/TinyOS_2.x_WG/12.20.2006
>