Fix the issue with tos-deluge not timing out properly.

[tinyos-2.x.git] / tos / interfaces / BlockWrite.nc

diff --git a/tos/interfaces/BlockWrite.nc b/tos/interfaces/BlockWrite.nc
index 7463f3c0f2741dfb96c88d9ecb74cbb01a3706b8..5ecd3d11dbc0ae07ae50a1a5669b472299215d1f 100644 (file)
--- a/tos/interfaces/BlockWrite.nc
+++ b/tos/interfaces/BlockWrite.nc
@@ -48,7 +48,7 @@ interface BlockWrite {
    * Between two erases, no byte may be written more than once.
    * 
    * @param addr starting address to begin write.
-   * @param buf buffer to write data from.
+   * @param 'void* COUNT(len) buf' buffer to write data from.
    * @param len number of bytes to write.
    * @return 
    *   <li>SUCCESS if the request was accepted, 
@@ -63,7 +63,7 @@ interface BlockWrite {
    * been completed.
    *
    * @param addr starting address of write.
-   * @param buf buffer that written data was read from.
+   * @param 'void* COUNT(len) buf' buffer that written data was read from.
    * @param len number of bytes written.
    * @param error SUCCESS if the operation was successful, FAIL if
    *   it failed
@@ -91,11 +91,10 @@ interface BlockWrite {
   event void eraseDone(error_t error);
 
   /**
-   * Initiate a sync operation and finialize any additional writes to
-   * the volume. A sync operation must be issued to ensure that data is
-   * stored in non-volatile storage. On SUCCES, the
-   * <code>syncDone</code> event will signal completion of the
-   * operation.
+   * Initiate a sync operation to finalize writes to the volume. A
+   * sync operation must be issued to ensure that data is stored in
+   * non-volatile storage. On SUCCES, the <code>syncDone</code> event
+   * will signal completion of the operation.
    *
    * @return 
    *   <li>SUCCESS if the request was accepted,