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

[Phil Levis]

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

Modified Files:
	tep114.txt 
Log Message:
Spelling errors, removed "asynchronicity", cut down on verbiage in intro.


Index: tep114.txt
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/txt/tep114.txt,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** tep114.txt	2 Jul 2008 19:31:57 -0000	1.10
--- tep114.txt	2 Jul 2008 19:38:46 -0000	1.11
***************
*** 6,11 ****
  :Group: Core Working Group
  :Type: Documentary 
! :Status: Draft
! :TinyOS-Version: 2.x
  :Author: Gilman Tolle, Philip Levis, and David Gay
  
--- 6,10 ----
  :Group: Core Working Group
  :Type: Documentary 
! :Status: Final
  :Author: Gilman Tolle, Philip Levis, and David Gay
  
***************
*** 55,65 ****
  
  Because sensing is an integral part of high-level application logic,
! the asynchronicity of these events means that high-level components
! must work with atomic section, even if the sampling rate is very low
  (e.g., every five minutes) and so could be easily placed in a
  task. Race conditions are problematic and possible in any real time
  multi-tasking design. Race conditions are a failure in design, and
! especially difficult to detect at low sampling rates. Careful and
! skillful design review practices flush out race conditions early on.
  
  Additionally, not all sensors require ADC conversions from the MCU.
--- 54,63 ----
  
  Because sensing is an integral part of high-level application logic,
! having asynchronous events means that high-level components
! must work with atomic sections, even if the sampling rate is very low
  (e.g., every five minutes) and so could be easily placed in a
  task. Race conditions are problematic and possible in any real time
  multi-tasking design. Race conditions are a failure in design, and
! especially difficult to detect at low sampling rates. 
  
  Additionally, not all sensors require ADC conversions from the MCU.
***************
*** 136,140 ****
  
  If the call to ``read`` has returned SUCCESS, but the ``readDone``
! event has not yet been signalled, then a subsequent call to ``read``
  MUST return EBUSY or FAIL.  This simple locking technique, as opposed
  to a more complex system in which multiple read/readDone pairs may be
--- 134,138 ----
  
  If the call to ``read`` has returned SUCCESS, but the ``readDone``
! event has not yet been signaled, then a subsequent call to ``read``
  MUST return EBUSY or FAIL.  This simple locking technique, as opposed
  to a more complex system in which multiple read/readDone pairs may be
***************
*** 231,235 ****
  After posting at least one buffer, the client can call read() with a
  specified sample period in terms of microseconds. The driver then
! begins to fill the buffers in the queue, signalling the bufferDone()
  event when a buffer has been filled. The client MAY call postBuffer()
  after read() in order to provide the device with new storage for
--- 229,233 ----
  After posting at least one buffer, the client can call read() with a
  specified sample period in terms of microseconds. The driver then
! begins to fill the buffers in the queue, signaling the bufferDone()
  event when a buffer has been filled. The client MAY call postBuffer()
  after read() in order to provide the device with new storage for