From a3f7a51c7ebce6e1e3fafac0d5e49724b269d833 Mon Sep 17 00:00:00 2001 From: scipio Date: Wed, 2 Jul 2008 19:42:13 +0000 Subject: [PATCH] Fixed section numbers. --- doc/html/tep114.html | 33 ++++++++++++--------------------- doc/txt/tep114.txt | 2 +- 2 files changed, 13 insertions(+), 22 deletions(-) diff --git a/doc/html/tep114.html b/doc/html/tep114.html index 9f4890e4..19e1f243 100644 --- a/doc/html/tep114.html +++ b/doc/html/tep114.html @@ -291,19 +291,11 @@ ul.auto-toc { Type:Documentary Status: -Draft +Final TinyOS-Version:2.x Author: Gilman Tolle, Philip Levis, and David Gay -Draft-Created:30-Oct-2005 - -Draft-Version:1.8 - -Draft-Modified:2007-09-18 - -Draft-Discuss:TinyOS Developer List <tinyos-devel at mail.millennium.berkeley.edu> -
@@ -342,13 +334,12 @@ interrupt-driven sampling. All of its commands and events are async and sensor values are always 16 bits, although only some subset of the bits may be significant (e.g., a 12-bit value).

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 +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. Careful and -skillful design review practices flush out race conditions early on.

+especially difficult to detect at low sampling rates.

Additionally, not all sensors require ADC conversions from the MCU. Many sensors today are digital. To sample these sensors, the MCU sends a sample command and receives the corresponding data over a bus (e.g., @@ -438,7 +429,7 @@ interface Read<val_t> { ReadWrite.readDone events is not SUCCESS, then the memory of the val parameter MUST be filled with zeroes.

If the call to read has returned SUCCESS, but the readDone -event has not yet been signalled, then a subsequent call to read +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 outstanding, is intended to reduce the complexity of SID client code.

@@ -523,7 +514,7 @@ drivers that may store the queue of buffers and count sizes by building a linked list.

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() +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 future reads.

@@ -570,12 +561,12 @@ connect a sensor into a more general system.

6. Author's Address

Gilman Tolle
-
2168 Shattuck Ave.
-
Arched Rock Corporation
-
Berkeley, CA 94704
+
501 2nd St. Ste 410
+
Arch Rock Corporation
+
San Francisco, CA 94107

-
phone - +1 510 981 8714
-
email - gtolle@archedrock.com
+
phone - +1 415 692 0828
+
email - gtolle@archrock.com


Philip Levis
@@ -599,7 +590,7 @@ connect a sensor into a more general system.

-

6. Citations

+

7. Citations

diff --git a/doc/txt/tep114.txt b/doc/txt/tep114.txt index 23ce7d39..235bf787 100644 --- a/doc/txt/tep114.txt +++ b/doc/txt/tep114.txt @@ -305,7 +305,7 @@ connect a sensor into a more general system. | email - david.e.gay@intel.com | -6. Citations +7. Citations ============================================================================ .. [1] TEP 108: Resource Arbitration. -- 2.39.2