RTOS/rtems
1
0
Fork 0
forked from Imagelibrary/rtems
Code Pull Requests Activity

2011-07-18 Sebastian Huber <sebastian.huber@embedded-brains.de>

Browse Source 
* user/mp.t: Avoid obsolete notation.
This commit is contained in:
Sebastian Huber
2011-07-18 09:19:06 +00:00
parent 3f3b773be1
commit 6f18b15bf6
2 changed files with 11 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/ChangeLog
View File

@@ -1,3 +1,7 @@
2011-07-18 Sebastian Huber <sebastian.huber@embedded-brains.de>
* user/mp.t: Avoid obsolete notation.
2011-07-15 Sebastian Huber <sebastian.huber@embedded-brains.de> 2011-07-15 Sebastian Huber <sebastian.huber@embedded-brains.de>
* user/part.t, user/sem.t: Typos. * user/part.t, user/sem.t: Typos.

14
doc/user/mp.t
View File

@@ -432,9 +432,9 @@ Many MPCI layers use the @code{packet_length} field of the
of the packet to avoid sending unnecessary data. This is especially of the packet to avoid sending unnecessary data. This is especially
useful if the media connecting the nodes is relatively slow. useful if the media connecting the nodes is relatively slow.
The to_convert field of the MP_packet_prefix portion of the packet indicates The @code{to_convert} field of the @code{rtems_packet_prefix} portion of the
how much of the packet (in @code{uint32_t}'s) may require packet indicates how much of the packet in 32-bit units may require conversion
conversion in a heterogeneous system. in a heterogeneous system.
@subsection Supporting Heterogeneous Environments @subsection Supporting Heterogeneous Environments
@@ -507,10 +507,10 @@ must be aware of the following:
@itemize @bullet @itemize @bullet
@item All packets must begin on a four byte boundary. @item All packets must begin on a four byte boundary.
@item Packets are composed of both RTEMS and application data. @item Packets are composed of both RTEMS and application data. All RTEMS data
All RTEMS data is treated as thirty-two (32) bit unsigned is treated as 32-bit unsigned quantities and is in the first @code{to_convert}
quantities and is in the first @code{@value{RPREFIX}MINIMUM_UNSIGNED32S_TO_CONVERT} 32-bit quantities of the packet. The @code{to_convert} field is part of the
thirty-two (32) quantities of the packet. @code{rtems_packet_prefix} portion of the packet.
@item The RTEMS data component of the packet must be in native @item The RTEMS data component of the packet must be in native
endian format. Endian conversion may be performed by either the endian format. Endian conversion may be performed by either the