Tue Nov 7 15:15:29 PST 2006

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

Modified Files:
      Tag: tinyos-2_0_devel-BRANCH
	overview.html porting.html tep1.html tep101.html tep102.html 
	tep103.html tep106.html tep107.html tep108.html tep109.html 
	tep110.html tep111.html tep112.html tep113.html tep114.html 
	tep115.html tep116.html tep117.html tep118.html tep119.html 
	tep120.html tep121.html tep123.html tep2.html tep3.html 
Log Message:
Fold changes back in.

Index: tep113.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep113.html,v
retrieving revision 1.1.2.11
retrieving revision 1.1.2.12
diff -C2 -d -r1.1.2.11 -r1.1.2.12
*** tep113.html	6 Nov 2006 20:00:39 -0000	1.1.2.11
--- tep113.html	7 Nov 2006 23:14:54 -0000	1.1.2.12
***************
*** 304,310 ****
  <tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">11-Jul-2005</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.1.2.5</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2006-11-06</td>
  </tr>
  <tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List &lt;tinyos-devel at mail.millennium.berkeley.edu&gt;</td>
--- 304,310 ----
  <tr class="field"><th class="docinfo-name">Draft-Created:</th><td class="field-body">11-Jul-2005</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Version:</th><td class="field-body">1.1.2.4</td>
  </tr>
! <tr class="field"><th class="docinfo-name">Draft-Modified:</th><td class="field-body">2006-06-14</td>
  </tr>
  <tr class="field"><th class="docinfo-name">Draft-Discuss:</th><td class="field-body">TinyOS Developer List &lt;tinyos-devel at mail.millennium.berkeley.edu&gt;</td>

Index: tep118.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep118.html,v
retrieving revision 1.1.2.5
retrieving revision 1.1.2.6
diff -C2 -d -r1.1.2.5 -r1.1.2.6
*** tep118.html	6 Nov 2006 20:00:41 -0000	1.1.2.5
--- tep118.html	7 Nov 2006 23:14:54 -0000	1.1.2.6
***************
*** 402,406 ****
  }
  </pre>
! <p>The t argument MUST be able to fit in a single message_t[<a class="reference" href="#id2">1</a>]  after
  considering the headers that the dissemination protocol introduces.
  A dissemination implementation SHOULD have a compile error if a larger
--- 402,406 ----
  }
  </pre>
! <p>The t argument MUST be able to fit in a single message_t[<a href="#id4" name="id5"><span class="problematic" id="id5">tep111_</span></a>]  after
  considering the headers that the dissemination protocol introduces.
  A dissemination implementation SHOULD have a compile error if a larger
***************
*** 517,520 ****
--- 517,526 ----
  </table>
  </div>
+ <div class="system-messages section">
+ <h1>Docutils System Messages</h1>
+ <div class="system-message" id="id4">
+ <p class="system-message-title">System Message: <a name="id4">ERROR/3</a> (<tt class="docutils">txt/tep118.txt</tt>, line 116); <em><a href="#id5">backlink</a></em></p>
+ Unknown target name: &quot;tep111&quot;.</div>
+ </div>
  </div>
  </body>

Index: tep119.html
===================================================================
RCS file: /cvsroot/tinyos/tinyos-2.x/doc/html/tep119.html,v
retrieving revision 1.1.2.5
retrieving revision 1.1.2.6
diff -C2 -d -r1.1.2.5 -r1.1.2.6
*** tep119.html	6 Nov 2006 20:00:41 -0000	1.1.2.5
--- tep119.html	7 Nov 2006 23:14:54 -0000	1.1.2.6
***************
*** 467,478 ****
  <p>Collection has a virtualized sending abstraction, the generic
  component CollectionSenderC:</p>
! <pre class="literal-block">
! generic configuration CollectionSenderC(collection_id_t collectid) {
!   provides {
!     interface Send;
!     interface Packet;
!   }
! }
! </pre>
  <p>This abstraction follows a similar virtualization approach to
  AMSenderC [<a class="reference" href="#id1">1</a>], except that it is parameterized by a collection_id_t
--- 467,490 ----
  <p>Collection has a virtualized sending abstraction, the generic
  component CollectionSenderC:</p>
! <div class="system-message">
! <p class="system-message-title">System Message: WARNING/2 (<tt class="docutils">txt/tep119.txt</tt>, line 198)</p>
! Literal block expected; none found.</div>
! <dl class="docutils">
! <dt>generic configuration CollectionSenderC(collection_id_t collectid) {</dt>
! <dd><dl class="first docutils">
! <dt>provides {</dt>
! <dd>interface Send;
! interface Packet;</dd>
! </dl>
! <div class="system-message">
! <p class="system-message-title">System Message: WARNING/2 (<tt class="docutils">txt/tep119.txt</tt>, line 202)</p>
! Definition list ends without a blank line; unexpected unindent.</div>
! <p class="last">}</p>
! </dd>
! </dl>
! <div class="system-message">
! <p class="system-message-title">System Message: WARNING/2 (<tt class="docutils">txt/tep119.txt</tt>, line 203)</p>
! Definition list ends without a blank line; unexpected unindent.</div>
! <p>}</p>
  <p>This abstraction follows a similar virtualization approach to
  AMSenderC [<a class="reference" href="#id1">1</a>], except that it is parameterized by a collection_id_t
***************
*** 498,549 ****
  neighbor. Link estimation can be done in a variety of ways, and we do
  not impose one here. It is decoupled from the establishment of
! routes. There is a narrow interface (LinkEstimator and
! NeighborTableEviction) between the link estimator and the routing
! engine. The one requirement is that the quality returned is
! standardized. A smaller return value from LinkEstimator.getQuality(),
! LinkEstimator.getforwardQuality(), LinkEstimator.getreserveQuality()
! MUST imply that the link to the neighbor is estimated to be of a
! higher quality than the one that results in a smaller return
! value. The range of value SHOULD be [0,255] and the variation in link
! quality in that range SHOULD be linear. Radio provided values such as
! LQI or RSI, beacon based link estimation to compute ETX, or their
! combination are some possible approaches to estimating link
! qualities. LinkEstimatorP MAY have its own control messages to compute
! bi-directional link qualities. LinkEstimatorP provides calls (txAck(),
! txNoAck(), and clearDLQ()) to update the link estimates based on
! successful or unsuccessful data transmission to the neighbors. The
! user of LinkEstimatorP can call insertNeighbor() to manually insert a
! node in the neighbor table, pinNeighbor() to prevent a neighbor from
! being evicted, and unpinNeighbor() to restore eviction policy:</p>
  <pre class="literal-block">
! typedef uint16_t neighbor_table_entry_t

  LinkEstimatorP {
    provides {
-     interface StdControl;
-     interface AMSend as Send;
-     interface Receive;
      interface LinkEstimator;
!     interface Init;
!     interface Packet;
!     interface LinkSrcPacket;
    }
  }

  interface LinkEstimator {
!   command uint8_t getLinkQuality(uint16_t neighbor);
!   command uint8_t getReverseQuality(uint16_t neighbor);
!   command uint8_t getForwardQuality(uint16_t neighbor);
!   command error_t insertNeighbor(am_addr_t neighbor);
!   command error_t pinNeighbor(am_addr_t neighbor);
!   command error_t unpinNeighbor(am_addr_t neighbor);
!   command error_t txAck(am_addr_t neighbor);
!   command error_t txNoAck(am_addr_t neighbor);
!   command error_t clearDLQ(am_addr_t neighbor);
!   event void evicted(am_addr_t neighbor);
  }

! interface NeighborTableEviction {
!   event void evicted(uint16_t neighbor)
  }
  </pre>
--- 510,543 ----
  neighbor. Link estimation can be done in a variety of ways, and we do
  not impose one here. It is decoupled from the establishment of
! routes. There is a narrow interface (LinkEstimator) between the link
! estimator and the routing engine. The one requirement is that the
! quality returned is standardized. A larger return value from
! LinkEstimator.getQuality(), LinkEstimator.getforwardQuality(),
! LinkEstimator.getreserveQuality() MUST imply that the link to the
! neighbor is estimated to be of a higher quality than the one that
! results in a smaller return value. The range of value SHOULD be
! [0,255] and the variation in link quality in that range SHOULD be
! linear. Radio provided values such as LQI or RSI, beacon based link
! estimation to compute ETX, or their combination are some possible
! approaches to estimating link qualities. LinkEstimatorP MAY have its
! own control messages to compute bi-directional link qualities:</p>
  <pre class="literal-block">
! typedef uint16_t neighbor_t

  LinkEstimatorP {
    provides {
      interface LinkEstimator;
!     interface NeighborTable;
    }
  }

  interface LinkEstimator {
!   command uint8_t getLinkQuality(neighbot_t neighbor);
!   command uint8_t getReverseQuality(neighbot_t neighbor);
!   command uint8_t getForwardQuality(neighbot_t neighbor);
  }

! interface NeighborTable {
!   event void evicted(neighbot_t neighbor)
  }
  </pre>