I remember the discussion now....
I guess the real question then is what the intended use is in this
case, as TOS_LOCAL_ADDRESS was used to indicate both the AM address
and the Node id in tinyos-1.x.
Kevin
On 3/9/06, Philip Levis <[EMAIL PROTECTED]> wrote:
> On Thu, 2006-03-09 at 13:55 -0600, Kevin Klues wrote:
> > Shouldn't the address not be accessed in this way anymore anyway? Is
> > it not better to wire to the ActiveMessageC component, and access it
> > through a call to adress() from the AMPacket interface.
> >
> > In your configuration you would have something like,
> >
> > configuration AppC {}
> > implementation {
> > components ActiveMessageC as AMRadio;
> >
> > MainC.SoftwareInit -> AMRadio;
> > App.AMPacket -> AMRadio;
> > }
> >
> > your implementation then accesses the address via...
> >
> > call AMPacket.address()
> >
> > instead of a direct usage of TOS_LOCAL_ADDRESS or TOS_NODE_ID
>
> There was a long discussion on this in the T2 list. The important point
> is that TOS_NODE_ID might not equal the AM address. The former is a
> unique identifier for the node, the second is a data link address. You
> access the address through calling a radio stack, but the former by
> accessing a global.
>
> I think that accessing NODE_ID through an interface is the cleaner
> approach, but the ease of use of a global won out in that discussion.
>
> Phil
>
> _______________________________________________
> Tinyos-devel mailing list
> [EMAIL PROTECTED]
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
