[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep107.txt,1.6,1.7

[Phil Levis]

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

Modified Files:
	tep107.txt 
Log Message:
Fixed links.


Index: tep107.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep107.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** tep107.txt	5 Feb 2007 19:06:56 -0000	1.6
--- tep107.txt	5 Feb 2007 19:59:12 -0000	1.7
***************
*** 255,259 ****
  (regardless of what components the OS uses) for low-power reasons:
  incorrectly configured pins can draw current and prevent the MCU from
! entering its lowest power sleep state[2_]. Clock calibration meets
  all three criteria. LED configuration is a special case: while it
  nominally meets all three criteria, the most important one is the third:
--- 255,259 ----
  (regardless of what components the OS uses) for low-power reasons:
  incorrectly configured pins can draw current and prevent the MCU from
! entering its lowest power sleep state [2]_. Clock calibration meets
  all three criteria. LED configuration is a special case: while it
  nominally meets all three criteria, the most important one is the third:
***************
*** 270,277 ****
  One common approach is for a configuration to "auto-wire" the
  initialization routines of its internal components. The configuration
! does not provide an Init interface. Virtualized services (TEP 108)
  often take this approach, as the service, rather than the clients, is
  what needs to be initialized. For example, the standard Timer
! virtualization (TEP 102), TimerMilliC, wires to TimerMilliP, which is
  a very simple configuration that takes the underlying implementation
  (HilTimerMilliC) and wires it to MainC::
--- 270,277 ----
  One common approach is for a configuration to "auto-wire" the
  initialization routines of its internal components. The configuration
! does not provide an Init interface. Virtualized services
  often take this approach, as the service, rather than the clients, is
  what needs to be initialized. For example, the standard Timer
! virtualization [3]_, TimerMilliC, wires to TimerMilliP, which is
  a very simple configuration that takes the underlying implementation
  (HilTimerMilliC) and wires it to MainC::
***************
*** 330,334 ****
  components.
  
! Unless part of a hardware abstraction architecture (HAA) [2]_, the
  Init.init() command MUST NOT assume that other components have been
  initialized unless it has initialized them, and MUST NOT call any
--- 330,334 ----
  components.
  
! Unless part of a hardware abstraction architecture (HAA) [4]_, the
  Init.init() command MUST NOT assume that other components have been
  initialized unless it has initialized them, and MUST NOT call any
***************
*** 378,381 ****
  .. [1] TEP 106: Schedulers and Tasks.
  
! .. [2] TEP 2: Hardware Abstraction Architecture. 
   
--- 378,386 ----
  .. [1] TEP 106: Schedulers and Tasks.
  
! .. [2] TEP 112: Microcontroller Power Management.
! 
! .. [3] TEP 102: Timers.
! 
! .. [4] TEP 2: Hardware Abstraction Architecture. 
!