[Tinyos Core WG] Meeting: 6/11

[Kevin Klues]

Plans are to check this in tomorrow morning if there are no
objections, major concerns with what is expressed in this mail.
Please read on....

Directory structure for threads:

tinyos-2.x
./apps
./apps/tosthreads
./apps/tosthreads/apps
./apps/tosthreads/apps/<...>
./apps/tosthreads/capps
./apps/tosthreads/capps/<...>
./apps/tosthreads/tutorials
./apps/tosthreads/tutorials/<...>
./tos
./tos/lib
./tos/lib/tosthreads
./tos/lib/tosthreads/chips
./tos/lib/tosthreads/chips/atm128
./tos/lib/tosthreads/chips/atm128/sim
./tos/lib/tosthreads/chips/atm1281
./tos/lib/tosthreads/chips/msp430
./tos/lib/tosthreads/chips/msp430/adc12
./tos/lib/tosthreads/chips/pxa27x
./tos/lib/tosthreads/csystem
./tos/lib/tosthreads/interfaces
./tos/lib/tosthreads/lib
./tos/lib/tosthreads/lib/printf
./tos/lib/tosthreads/platforms
./tos/lib/tosthreads/platforms/mica2
./tos/lib/tosthreads/platforms/mica2/chips
./tos/lib/tosthreads/platforms/mica2/chips/cc1000
./tos/lib/tosthreads/platforms/telosa
./tos/lib/tosthreads/sensorboards
./tos/lib/tosthreads/sensorboards/tmote_onboard
./tos/lib/tosthreads/system
./tos/lib/tosthreads/types

This is the basic directory structure I am proposing.  A few more
directories may be added, but the overall structure will remain the
same.  As I said in the last email (and as can be seen above),
everything for thread support is currently encapsulated underneath the
tos/lib/tosthreads directory by shadowing the appropriate source files
from the primary system, platform, and chip directories in the core
trunk.  This provides isolation of threads from the rest of the system
for purposes of the release, and gives us time to find the best method
of integration after.

I jsut wanted to get peoples thoughts on this directory structure and
see if anyone has any problems with it.  Also, the proposed targets
for compileing with thread support are: threads, cthreads, and
dynthreads.

i.e. 'make telosb threads' or 'make telosb cthreads' or 'make telosb dynthreads'

the 'threads' target is for normal nesC based thread support, the
'cthreads' target is for compiling applications written completely in
C using the C based API, and the 'dynthreads' target is for compiling
C based thread applications for dynamic linking and loading at
runtime.  While this third one (i.e. the 'dynthreads' target) is
currently implemented and working properly, we don't plan to release
the code for actually performing a dynamic load yet since the code for
doing so is not quite as mature as the thread code itself.  More than
anything, I just wanted to get feedback on the names of these targets
to see if everyone thinks they are appropriate.  So what do you think?

Last, but not least, as I said on the call, right now there are a few
modifications needed to the .target files of any supported platforms
in order to enable thread support, but I think I may know a way around
this.  It obviously makes more sense to explicitly list out the
supported targets within the threads.extra, cthreads.extra, and
dynthreads.extra targets explicitly, and I'm going to look into how to
get this to work.  I think I may know a way.

I plan to check all of this in tomorrow morning, so please get back to
me before then if you have any problems with anything listed here.

Kevin

On Tue, Jun 10, 2008 at 10:57 PM, Philip Levis <pal at cs.stanford.edu> wrote:
> Wednesday, June 11, 2008, 09:30 AM US Pacific Time
> Bridge: 1
> Passcode: 9713699
>
> 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:
>
> Status
>   - 802.15.4 base station app (Phil)
>   - TEP 114 (Phil)
> Threads (Kevin)
> Release plan
>   Safe TinyOS
>   nesC 1.3
>   Code freeze, 6/16
>   Documentation to-dos
>
> 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