[Tinyos-2-commits] CVS: tinyos-2.x/doc/txt tep111.txt, 1.5, 1.6 tep112.txt, 1.6, 1.7 tep114.txt, 1.6, 1.7 tep119.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-serv22956/txt

Modified Files:
	tep111.txt tep112.txt tep114.txt tep119.txt 
Log Message:
TEP updates for last call.


Index: tep111.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep111.txt,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** tep111.txt	12 Dec 2006 18:22:54 -0000	1.5
--- tep111.txt	10 Jan 2007 18:33:38 -0000	1.6
***************
*** 145,149 ****
    } message_t;
  
! This format keeps data at a fixed offset, which is important when
  passing a message buffer between two different link layers. If the
  data payload were at different offsets for different link layers, then
--- 145,150 ----
    } message_t;
  
! This format keeps data at a fixed but platform dependent offset, which 
! is important when
  passing a message buffer between two different link layers. If the
  data payload were at different offsets for different link layers, then

Index: tep112.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep112.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** tep112.txt	20 Dec 2006 03:02:38 -0000	1.6
--- tep112.txt	10 Jan 2007 18:33:38 -0000	1.7
***************
*** 98,102 ****
  issue on very low power microcontrollers, such as the Atmega128 and
  MSP430, more powerful processors, such as the Xscale family (the basis
! of platforms such as the imote2) can power states with wakeup
  latencies as large as 5ms. For some application domains, this latency
  could be a serious issue. Higher level components therefore need a way
--- 98,102 ----
  issue on very low power microcontrollers, such as the Atmega128 and
  MSP430, more powerful processors, such as the Xscale family (the basis
! of platforms such as the imote2) can have power states with wakeup
  latencies as large as 5ms. For some application domains, this latency
  could be a serious issue. Higher level components therefore need a way
***************
*** 257,263 ****
  At the HIL level, TinyOS subsystems generally have a simple,
  imperative power management interface. Depending on the latencies
! involved, this interface is either ``StdControl`` or ``SplitControl``.
  These interfaces are imperative in that when any component calls
! ``StdControl.stop`` on another component, it causes the subsystem that
  component represents to enter an inactive, low-power state.
  
--- 257,264 ----
  At the HIL level, TinyOS subsystems generally have a simple,
  imperative power management interface. Depending on the latencies
! involved, this interface is either ``StdControl``, ``SplitControl``,
! or ``AsyncStdControl``.
  These interfaces are imperative in that when any component calls
! ``stop`` on another component, it causes the subsystem that
  component represents to enter an inactive, low-power state.
  

Index: tep114.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep114.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** tep114.txt	12 Dec 2006 18:22:54 -0000	1.6
--- tep114.txt	10 Jan 2007 18:33:38 -0000	1.7
***************
*** 63,67 ****
  a sample command and receives the corresponding data over a bus (e.g.,
  SPI, I2C). The latency involved, combined with possible Resource
! arbitration [_tep108], means that these bus operations are often
  synchronous code. In the command direction, this can force a task
  allocation to convert async to sync; in the event direction, the
--- 63,67 ----
  a sample command and receives the corresponding data over a bus (e.g.,
  SPI, I2C). The latency involved, combined with possible Resource
! arbitration [1]_, means that these bus operations are often
  synchronous code. In the command direction, this can force a task
  allocation to convert async to sync; in the event direction, the
***************
*** 69,73 ****
  practice, in a task.
  
! Finallly, the simplicity of the ADC interface has led many sensors to
  introduce several new ones for calibration and control, such as
  ``Mic`` and ``MagSetting``. Because ADCs generally do not have error
--- 69,73 ----
  practice, in a task.
  
! Finally, the simplicity of the ADC interface has led many sensors to
  introduce several new ones for calibration and control, such as
  ``Mic`` and ``MagSetting``. Because ADCs generally do not have error
***************
*** 375,376 ****
--- 375,381 ----
  |
  
+ 6. Citations
+ ============================================================================
+ 
+ .. [1] TEP 108: Resource Arbitration.
+ 

Index: tep119.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep119.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** tep119.txt	12 Dec 2006 18:22:54 -0000	1.6
--- tep119.txt	10 Jan 2007 18:33:38 -0000	1.7
***************
*** 205,210 ****
    }
  
- 
- 
  This abstraction follows a similar virtualization approach to
  AMSenderC [1_], except that it is parameterized by a collection_id_t
--- 205,208 ----