[Tinyos Core WG] new tag

[Vlado Handziski]

All of the platforms below use the same msp430 chip as telosb. The HIL apps
like Blink, RadioCountToLeds, etc. should be tested on them in normal and
safe variants. Why should there be problems? I hope that platform specific
components (apart from the common mcu abstraction) without any deputy
annotations are just ignored /treated safe)?

Vlado

On Sun, Jun 22, 2008 at 01:30, John Regehr <regehr at cs.utah.edu> wrote:

> Hi folks,
>
> It's not likely that the safe version of any app for platforms other than
> mica2, micaz, telosb work until someone has specifically gone in and made
> sure that these work (which we haven't done).
>
> John
>
>
>
> Vlado Handziski wrote:
>
>> Those testing the safe versions on eyesIFX, shimmer, tinynode, etc. should
>> update their .platform/.family files, I copied the missing CIL_MACHINE
>> definition from telosb.
>>
>> Vlado
>>
>> On Sat, Jun 21, 2008 at 00:09, Philip Levis <pal at cs.stanford.edu <mailto:
>> pal at cs.stanford.edu>> wrote:
>>
>>    There were a couple of (late!!!!) last-minute checkins after I tagged
>>    with rc1, so I've now tagged with an rc2. Please do your testing with
>>    tag:
>>
>>    rc_2_tinyos_2_1_0
>>
>>    Apologies if you've already started testing. I would have had to tag
>>    with rc2 regardless, so you would have needed to repeat regardless.
>>
>>    Also, a note: no-one should *ever* move the release testing tags. Once
>>    applied, they should never change. Instead, if there modifications, I
>>    apply a new release candidate (e.g., rc3).
>>
>>    Finally, application owners have an additional responsibility. TEP 4
>>    lays out how active message IDs should be allocated. If you own an
>>    application, you should check that it follows TEP 4. Basically, this
>>    means stuff in apps should have AM ids between 128-255; below 128 is
>>    reserved for tos/. If your application has an ID in the range of
>>    0-127, you should change it and apply that change to the tree. When I
>>    apply rc3 we can do a quick sanity check.
>>
>>    Phil
>>    _______________________________________________
>>    Tinyos-2.0wg mailing list
>>    Tinyos-2.0wg at millennium.berkeley.edu
>>    <mailto:Tinyos-2.0wg at millennium.berkeley.edu>
>>
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Tinyos-2.0wg mailing list
>> Tinyos-2.0wg at millennium.berkeley.edu
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-2.0wg/attachments/20080622/0fe011af/attachment.htm