[Tinyos Core WG] Meeting: 5/28 (another full agenda)

[Kevin Klues]

I've verified that adding threading support and allowing one to do a
'make telosb threads' does not increase any ROM or RAM usage on
telosb, mica2, and micaz platforms when doing a normal 'make telosb',
etc -- apps compiled without the 'threads' target remain unchanged.

Right now I have all files where interrupt handlers are defined with
thread support duplicated under the appropriate
tos/lib/tosthreads/chips/MCUXXX directory.  I think for now this might
be the best route to take for the release, with migration into the
core chip directories after the release.  With this approach, there is
no modification needed to any core system files, and all files used by
tosthreads are self-contained somewhere under the lib/tosthreads
directory.

Obviously integration into the core system directories is desired at
some point for maintenance purposes, but I think the separation is
appropriate for the release, given that the release provides a
snapshot where maintenance is not important, and we haven't come to
full agreement yet on how the full integration should be made.

What do people think?  If this sounds good, I can start checking stuff
in.  I'm sure we'll talk about it tomorrow on the call though...

Kevin

On Tue, May 27, 2008 at 10:48 PM, Philip Levis <pal at cs.stanford.edu> wrote:
> Wednesday, May 28, 2008, 09:30 AM US Pacific Time
> Bridge: 1
> Passcode: 2989080
>
> US: 1-916-356-2663 or 1-888-875-9370 (non-Intel)
> UK: +44 1793 402663
> Denmark: +45 4527 5090
> Germany: +44 01793 402663 (Munich)
>          +44 01793 402663 (Braunschweig)
>          +44 01793 402663 (Ulm)
>
> Agenda:
>
> 1. LPL (David Moss and Phil Levis)
>     - Interface and API (compile vs. runtime, etc.)
>     - action on cancel()
> 2. Threads (Kevin)
>     - Source changes
>     - Makefile changes
> 3. Safe TinyOS (John Regehr)
>     - interface annotations
>     - Toolchain requirements
> 4. Send virtualization (Phil, Vlado, and David M.)
>     - AMSenderC vs. ActiveMessageC
>     - per-packet versus per-stack state
> 5. MSP430-gcc (Vlado)
> 6. Code changes (Jan H.)
>     - VirtualizeAlarmC on MSP430 to uint32_t
>     - Init on PoolC and QueueC
>     - Adding ENOACK to TinyError.h
>     - Interfaces (GetNow, SetNow, AsyncSplitControl)
>
> Phil
>
> _______________________________________________
> Tinyos-2.0wg mailing list
> Tinyos-2.0wg at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg
>



-- 
~Kevin