[Tinyos-host-mote-wg] [Tinyos-2.0wg] Virtualized Alarms

[Phil Buonadonna]

So, I apologize for 'flooding the list'. As I'm trying to port the timer
subsystem to a new platform, I'm trying to make sense of TEP 102 and the
existing implementations.

This question concerns Alarms.

Both the required alarm configurations (Alarm32khzC and AlarmMilliC) are
generics => each new instantiation results in a completely independent
Alarm.  This implies the underlying mechanisms does some kind of
virtualization OR maps to unique hardware resources.

The atm128 implementation of Alarm32khzC seems to collapse all
instantiations of the configuration onto a single component. Is this true?
Thus any additional instantiations of the alarm will results in a
catastrophic cacophony of alarmage.

The msp implementation seems to do better, although each alarm instantiation
is mapped to a single hardware resource.  The TEP, however, does not define
a minimum number of channels. Should it?

An answer of "yes, that's just the way it is now" is fine, but just to get
clear on things.

pb

Phil Buonadonna
Arched Rock Corp.
2168 Shattuck Ave. 2nd Floor
Berkeley, CA 94704
pbuonadonna at archedrock.com
(510) 981-8714 - Voice
(510) 868-1769 - Fax 

_______________________________________________
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