Commit 437c349a authored by Philippe Gerum's avatar Philippe Gerum

doc: prebuild

parent 501ec6af
......@@ -1355,6 +1355,9 @@ is subject to change with ABI revisions.
from the appropriate RTDM driver the file descriptor is connected
to.
- A Cobalt replacement for fcntl(2) has been introduced. The
implementation currently deals with the O_NONBLOCK flag exclusively.
- Cobalt's select(2) service is not automatically restarted anymore
upon Linux signal receipt, conforming to the POSIX standard (see man
signal(7)). In such an event, -1 is returned and errno is set to
......@@ -1669,6 +1672,12 @@ An emulation of rt_alarm_wait() is available from the
=== Message pipes ===
- +rt_pipe_create()+ now returns the minor number assigned to the
connection, matching the /dev/rtp<minor> device usable by the
regular threads. As a consequence of this, any return value higher
or equal to zero denotes a successful operation, a negative return
denotes an error.
- Writing to a message pipe is allowed from all contexts, including
from alarm handlers.
......
......@@ -88,15 +88,15 @@ located at `/home/me/linux-3.10-ipipe` in order to patch the Xenomai
support in:
------------------------------------------------------------------------------
$ cd xenomai-forge
$ cd xenomai-3
$ scripts/prepare-kernel.sh --linux=/home/me/linux-3.10
------------------------------------------------------------------------------
Note: The script will infer the location of the Xenomai kernel code
from its own location within the Xenomai source tree. For instance, if
`/home/me/xenomai-forge/scripts/prepare-kernel.sh` is executing, then
`/home/me/xenomai-3/scripts/prepare-kernel.sh` is executing, then
the Xenomai kernel code available from
`/home/me/xenomai-forge/kernel/cobalt` will be patched in the target
`/home/me/xenomai-3/kernel/cobalt` will be patched in the target
Linux kernel.
......
......@@ -980,10 +980,10 @@ of all timers from the registered Xenomai clocks.
</dd>
</dl></div>
<div class="paragraph"><p>There is no kernel-based time base management anymore with Xenomai
3.0-rc1. Functionally speaking, only the former <em>master</em> time base
3.0-rc2. Functionally speaking, only the former <em>master</em> time base
remains, periodic timing is now controlled locally from the Xenomai
libraries in user-space.</p></div>
<div class="paragraph"><p>Xenomai 3.0-rc1 defines a built-in clock named <em>coreclk</em>, which has
<div class="paragraph"><p>Xenomai 3.0-rc2 defines a built-in clock named <em>coreclk</em>, which has
the same properties than the former <em>master</em> time base available with
Xenomai 2.x (i.e. tickless with nanosecond resolution).</p></div>
<div class="paragraph"><p>The settings of existing clocks can be read from entries under the new
......@@ -2489,6 +2489,12 @@ A Cobalt replacement for mmap(2) has been introduced. The
</li>
<li>
<p>
A Cobalt replacement for fcntl(2) has been introduced. The
implementation currently deals with the O_NONBLOCK flag exclusively.
</p>
</li>
<li>
<p>
Cobalt&#8217;s select(2) service is not automatically restarted anymore
upon Linux signal receipt, conforming to the POSIX standard (see man
signal(7)). In such an event, -1 is returned and errno is set to
......@@ -3080,6 +3086,15 @@ field <code>active</code> has been added, to reflect the current state of
<div class="ulist"><ul>
<li>
<p>
<code>rt_pipe_create()</code> now returns the minor number assigned to the
connection, matching the /dev/rtp&lt;minor&gt; device usable by the
regular threads. As a consequence of this, any return value higher
or equal to zero denotes a successful operation, a negative return
denotes an error.
</p>
</li>
<li>
<p>
Writing to a message pipe is allowed from all contexts, including
from alarm handlers.
</p>
......@@ -3221,7 +3236,7 @@ CC = $(shell $(CONFIG_CMD) --cc)</code></pre>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated 2014-10-04 18:47:11 CEST
Last updated 2014-10-31 12:36:14 CET
</div>
</div>
</body>
......
......@@ -997,7 +997,7 @@ package is called <em>valgrind-devel</em> on Fedora.</td>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated 2014-10-04 18:47:11 CEST
Last updated 2014-10-31 12:36:14 CET
</div>
</div>
</body>
......
......@@ -840,14 +840,14 @@ located at <code>/home/me/linux-3.10-ipipe</code> in order to patch the Xenomai
support in:</p></div>
<div class="listingblock">
<div class="content">
<pre><code>$ cd xenomai-forge
<pre><code>$ cd xenomai-3
$ scripts/prepare-kernel.sh --linux=/home/me/linux-3.10</code></pre>
</div></div>
<div class="paragraph"><p>Note: The script will infer the location of the Xenomai kernel code
from its own location within the Xenomai source tree. For instance, if
<code>/home/me/xenomai-forge/scripts/prepare-kernel.sh</code> is executing, then
<code>/home/me/xenomai-3/scripts/prepare-kernel.sh</code> is executing, then
the Xenomai kernel code available from
<code>/home/me/xenomai-forge/kernel/cobalt</code> will be patched in the target
<code>/home/me/xenomai-3/kernel/cobalt</code> will be patched in the target
Linux kernel.</p></div>
</div>
<div class="sect2">
......@@ -1870,7 +1870,7 @@ Xenomai 3.x, you should have a look at
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated 2014-10-04 18:47:11 CEST
Last updated 2014-10-31 12:36:14 CET
</div>
</div>
</body>
......
......@@ -1452,7 +1452,7 @@ rebuilding the kernel.</p></div>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated 2014-10-04 18:47:11 CEST
Last updated 2014-10-31 12:36:14 CET
</div>
</div>
</body>
......
......@@ -763,7 +763,7 @@ specific
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated 2014-10-04 18:47:11 CEST
Last updated 2014-10-31 12:36:14 CET
</div>
</div>
</body>
......
......@@ -941,7 +941,7 @@ running the auto-tuner after each boot e.g:</p></div>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">