[Tinyos-host-mote-wg] Re: [Tinyos-2.0wg] Bridge, agenda for TinyOS 2.x 10/5

[Philip Levis]

On Wed, 2005-10-05 at 02:16 -0700, Joe Polastre wrote:

> You need to clear up your terminology.  Up to this point, radios in
> TinyOS have included their MAC protocol within the radio code.  What I
> recommend is a different structuring of the radio stacks, one where
> the packet send and receive mechanisms are the radio "driver" and then
> the MAC protocol is built on top of that.  S-MAC employed this method
> a few years ago, and I think it is the right way to go.  Then you
> build your MAC protocols above the radio packet driver.

Depends on the MAC. It doesn't make a lot of sense for CSMA (or other
protocols that do not have control packets). But it makes a lot of sense
for TDMA (or other protocols that do have control packets).

The mica RFM radio stack didn't include the MAC in the radio code. The
MAC was implemented in ChannelMonC, which was separate from
MicaHighSpeedRadioM. Jason did this partially as a response to
UCLA/ISI's observations that SEC_DED in the rene stack had all of the
logic in it (pure layering was problematic). The mica2 saw the
transition back to big, monolithic radio stacks.

Phil

_______________________________________________
Tinyos-2.0wg mailing list
Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg