[Tinyos-devel] Message_t thoughts: prototypes

[Eric Decker]

But for this to work I need to decouple the AM encapsulation from what
outputport the packet needs to go out.  Currently there is a one to one
coupling between
an AM instance and either SerialAM... or Radio which when AM.settype etc
gets
called then fills in the fields in the serial header or radio header.  Which
doesn't work
if we are queued and we don't know which port we are going out yet.

So I am reworking the current AM implementation to use an AM header which
then
gets removed and subsumed when the packet is handed to the serial or radio
h/w.
Structurally and functionally works much better and the schemes that are
being discussed
are congruent with it as well.

eric


On Sun, May 24, 2009 at 7:54 AM, Miklos Maroti <mmaroti at math.u-szeged.hu>wrote:

> > What would this switch in the metadata do?  One needs to be careful when
> > structuring things this way.  The switch I'm talking about radio vs.
> serial
> > is actually controlled by an event and doesn't associate itself with a
> > packet so what would the metadata control cell do?  Rather the
> determination
> > of what output port the packet should go out is made when the packet is
> > ready to go out.  The Send occurs and the final output header added to
> the
> > packet and then handed to the hardware.
>
> Oh I see, then that is even easier I think. No metadata is needed.
>
> Miklos
>



-- 
Eric B. Decker
Senior (over 50 :-) Researcher
Autonomous Systems Lab
Jack Baskin School of Engineering
UCSC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-devel/attachments/20090526/ffbccb91/attachment.htm