[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep102.txt,1.9,1.10

[David Gay]

Update of /cvsroot/tinyos/tinyos-2.x/doc/txt
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv12879/txt

Modified Files:
	tep102.txt 
Log Message:
102 updates from Ben Greenstein


Index: tep102.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep102.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** tep102.txt	23 May 2007 21:41:58 -0000	1.9
--- tep102.txt	11 Jun 2007 20:42:35 -0000	1.10
***************
*** 88,96 ****
  
  Examples of widths are 8-bit, 16-bit, 32-bit, and 64-bit.  The width
! for timer interfaces and components SHOULD be 32-bits.  That is, for
! lack of a good reason, timer interfaces should expose a 32-bit
! interface.  In a number of circumstances there are good reasons not
! to expose a 32-bit interface.  This TEP emphasizes 32-bit widths
! while reasonably accommodating other widths.
  
  Accuracy reflects how closely a component conforms to the precision it
--- 88,95 ----
  
  Examples of widths are 8-bit, 16-bit, 32-bit, and 64-bit.  The width
! for timer interfaces and components SHOULD be 32-bits.  This TEP
! emphasizes 32-bit widths while reasonably accommodating other widths -
! a particular platform may have good reasons not to expose a 32-bit
! interface.
  
  Accuracy reflects how closely a component conforms to the precision it
***************
*** 204,208 ****
  
  fired() 
!   signals that the alarm has occurred.
  
  isRunning() 
--- 203,207 ----
  
  fired() 
!   signals that the alarm has expired.
  
  isRunning() 
***************
*** 243,247 ****
  BusyWait blocks for no less than the specified amount of time.  No
  explicit upper bound is imposed on the enacted delay, though it is
! expected the underlying implementation spins in a busy loop until
  the specified amount of time has elapsed.
  ::
--- 242,246 ----
  BusyWait blocks for no less than the specified amount of time.  No
  explicit upper bound is imposed on the enacted delay, though it is
! expected that the underlying implementation spins in a busy loop until
  the specified amount of time has elapsed.
  ::
***************
*** 312,320 ****
  
  fired()
!   signals that the timer has occurred.
  
  isRunning() 
    return TRUE if the timer has been started and has not been cancelled
!   and has not fired for the case of one-shot timers.  One a periodic
    timer is started, isRunning will return TRUE until it is cancelled.
  
--- 311,319 ----
  
  fired()
!   signals that the timer has expired (one-shot) or repeated (periodic).
  
  isRunning() 
    return TRUE if the timer has been started and has not been cancelled
!   and has not fired for the case of one-shot timers.  Once a periodic
    timer is started, isRunning will return TRUE until it is cancelled.
  
***************
*** 393,398 ****
    }
  
! This pattern MAY be used to defined components for the platform that
! are mutually incompatible in single application.  Incompatible
  components SHOULD produce compile-time errors when compiled
  together.
--- 392,397 ----
    }
  
! This pattern MAY be used to define components for the platform that
! are mutually incompatible in a single application.  Incompatible
  components SHOULD produce compile-time errors when compiled
  together.
***************
*** 598,602 ****
    * ``VirtualizeTimerC.nc``
  
! The implementation of Timers for the MSP430 is in
  ``tinyos-2.x/tos/chips/msp430/timer``:
  
--- 597,601 ----
    * ``VirtualizeTimerC.nc``
  
! The implementation of timers for the MSP430 is in
  ``tinyos-2.x/tos/chips/msp430/timer``:
  
***************
*** 640,643 ****
--- 639,647 ----
      special function registers
  
+ Implementation of timers for the ATmega128 and PXA27x may be found in
+ ``tinyos-2.x/tos/chips/atm128/timer`` and
+ ``tinyos-2.x/tos/chips/pxa27x/timer`` respectively.
+ 
+ 
  7. Author's Address
  ====================================================================