change log for rtems (2011-07-18)

rtems-vc at rtems.org rtems-vc at rtems.org
Mon Jul 18 10:10:19 UTC 2011


 *sh*:
2011-07-18	Sebastian Huber <sebastian.huber at embedded-brains.de>

	* user/mp.t: Avoid obsolete notation.

M  1.315  doc/ChangeLog
M   1.17  doc/user/mp.t

diff -u rtems/doc/ChangeLog:1.314 rtems/doc/ChangeLog:1.315
--- rtems/doc/ChangeLog:1.314	Fri Jul 15 08:36:55 2011
+++ rtems/doc/ChangeLog	Mon Jul 18 04:19:06 2011
@@ -1,3 +1,7 @@
+2011-07-18	Sebastian Huber <sebastian.huber at embedded-brains.de>
+
+	* user/mp.t: Avoid obsolete notation.
+
 2011-07-15	Sebastian Huber <sebastian.huber at embedded-brains.de>
 
 	* user/part.t, user/sem.t: Typos.

diff -u rtems/doc/user/mp.t:1.16 rtems/doc/user/mp.t:1.17
--- rtems/doc/user/mp.t:1.16	Thu Aug 21 09:50:16 2008
+++ rtems/doc/user/mp.t	Mon Jul 18 04:19:06 2011
@@ -432,9 +432,9 @@
 of the packet to avoid sending unnecessary data.  This is especially 
 useful if the media connecting the nodes is relatively slow.
 
-The to_convert field of the MP_packet_prefix portion of the packet indicates
-how much of the packet (in @code{uint32_t}'s) may require
-conversion in a heterogeneous system.
+The @code{to_convert} field of the @code{rtems_packet_prefix} portion of the
+packet indicates how much of the packet in 32-bit units may require conversion
+in a heterogeneous system.
 
 @subsection Supporting Heterogeneous Environments
 
@@ -507,10 +507,10 @@
 @itemize @bullet
 @item All packets must begin on a four byte boundary.
 
- at item Packets are composed of both RTEMS and application data.
-All RTEMS data is treated as thirty-two (32) bit unsigned
-quantities and is in the first @code{@value{RPREFIX}MINIMUM_UNSIGNED32S_TO_CONVERT}
-thirty-two (32) quantities of the packet.
+ at item Packets are composed of both RTEMS and application data.  All RTEMS data
+is treated as 32-bit unsigned quantities and is in the first @code{to_convert}
+32-bit quantities of the packet.  The @code{to_convert} field is part of the
+ at code{rtems_packet_prefix} portion of the packet.
 
 @item The RTEMS data component of the packet must be in native
 endian format.  Endian conversion may be performed by either the



--

Generated by Deluxe Loginfo [http://www.codewiz.org/projects/index.html#loginfo] 2.122 by Bernardo Innocenti <bernie at develer.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/vc/attachments/20110718/cfd52082/attachment.html>


More information about the vc mailing list