Commit b132977a authored by Philippe Gerum's avatar Philippe Gerum

doc: regenerate documentation

parent fc9b0e5d
......@@ -354,7 +354,7 @@ although this is not mandatory if building with `--disable-tls`.
tree (git.xenomai.org), the autoconf (>= 2.62), automake and libtool
packages must be available on your build system. This is not
required when building from a source tree extracted from a
http://download.gna.org/xenomai/[release tarball].
link:/downloads/xenomai/[release tarball].
_Cobalt_-specific requirements
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
......@@ -363,7 +363,7 @@ _Cobalt_-specific requirements
- An interrupt pipeline (I-pipe) patch must be available for your
target kernel. You can find the official patches issued by the
Xenomai project http://download.gna.org/adeos/patches/v3.x/[there].
Xenomai project link:/downloads/ipipe/[there].
Only patches from the *ipipe-core* series are appropriate, legacy
patches from the *adeos-ipipe* series are not.
......@@ -390,10 +390,9 @@ source tree:
$ ./scripts/bootstrap
---------------------
If building from a http://download.gna.org/xenomai[release tarball], a
set of autoconf-generated file will be readily available from the
extracted source tree, and therefore reconfiguring will not be
required.
If building from a link:/downloads/xenomai/[release tarball], a set of
autoconf-generated file will be readily available from the extracted
source tree, and therefore reconfiguring will not be required.
When run, the generated `configure` script prepares for building the
libraries and programs, for both the _Cobalt_ and _Mercury_ cores. The
......
......@@ -3461,7 +3461,7 @@ CC = $(shell $(CONFIG_CMD) --cc)</code></pre>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated 2015-06-21 15:55:29 CEST
Last updated 2015-06-23 15:36:01 CEST
</div>
</div>
</body>
......
......@@ -850,7 +850,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 2015-06-21 15:55:29 CEST
Last updated 2015-06-23 15:36:01 CEST
</div>
</div>
</body>
......
......@@ -1142,7 +1142,7 @@ If you plan to build from the sources available from the Xenomai GIT
tree (git.xenomai.org), the autoconf (&gt;= 2.62), automake and libtool
packages must be available on your build system. This is not
required when building from a source tree extracted from a
<a href="http://download.gna.org/xenomai/">release tarball</a>.
<a href="/downloads/xenomai/">release tarball</a>.
</p>
</li>
</ul></div>
......@@ -1159,7 +1159,7 @@ The kernel version must be 3.10 or better.
<p>
An interrupt pipeline (I-pipe) patch must be available for your
target kernel. You can find the official patches issued by the
Xenomai project <a href="http://download.gna.org/adeos/patches/v3.x/">there</a>.
Xenomai project <a href="/downloads/ipipe/">there</a>.
Only patches from the <strong>ipipe-core</strong> series are appropriate, legacy
patches from the <strong>adeos-ipipe</strong> series are not.
</p>
......@@ -1196,10 +1196,9 @@ source tree:</p></div>
<div class="content">
<pre><code>$ ./scripts/bootstrap</code></pre>
</div></div>
<div class="paragraph"><p>If building from a <a href="http://download.gna.org/xenomai">release tarball</a>, a
set of autoconf-generated file will be readily available from the
extracted source tree, and therefore reconfiguring will not be
required.</p></div>
<div class="paragraph"><p>If building from a <a href="/downloads/xenomai/">release tarball</a>, a set of
autoconf-generated file will be readily available from the extracted
source tree, and therefore reconfiguring will not be required.</p></div>
<div class="paragraph"><p>When run, the generated <code>configure</code> script prepares for building the
libraries and programs, for both the <em>Cobalt</em> and <em>Mercury</em> cores. The
core-specific code which may be needed internally is automatically and
......@@ -2027,7 +2026,7 @@ Xenomai 3.x, you should have a look at
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated 2015-06-21 15:55:29 CEST
Last updated 2015-06-23 15:36:01 CEST
</div>
</div>
</body>
......
......@@ -1455,7 +1455,7 @@ allocation requests.</p></div>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated 2015-06-21 15:55:29 CEST
Last updated 2015-06-23 15:36:01 CEST
</div>
</div>
</body>
......
......@@ -763,7 +763,7 @@ specific
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated 2015-06-21 15:55:29 CEST
Last updated 2015-06-23 15:36:01 CEST
</div>
</div>
</body>
......
......@@ -193,7 +193,7 @@ UDD_IOCTL</h2></td></tr>
</div><div class="memdoc">
<p>IRQ directly managed from the mini-driver on top of the UDD core. </p>
<p>The mini-driver is in charge of notifying the Cobalt threads waiting for IRQ events by calling the <a class="el" href="group__rtdm__udd.html#ga7bd19086f467b6ba791690a565d2c509" title="Notify an IRQ event for an unmanaged interrupt. ">udd_notify_event()</a> service. </p>
<p>The mini-driver is in charge of attaching the handler(s) to the IRQ(s) it manages, notifying the Cobalt threads waiting for IRQ events by calling the <a class="el" href="group__rtdm__udd.html#ga7bd19086f467b6ba791690a565d2c509" title="Notify an IRQ event for an unmanaged interrupt. ">udd_notify_event()</a> service. </p>
<p>Referenced by <a class="el" href="group__rtdm__udd.html#gaafa15680426042c8c411b6fcf10627da">udd_disable_irq()</a>, <a class="el" href="group__rtdm__udd.html#ga7ee451ee6e96cbb88254877ca5dd5d3f">udd_enable_irq()</a>, <a class="el" href="group__rtdm__udd.html#gaa5bee7471396c7b182a5a2a5fb60d230">udd_register_device()</a>, and <a class="el" href="group__rtdm__udd.html#ga389544ffa49f17fe3417d97122ed3acb">udd_unregister_device()</a>.</p>
......@@ -460,7 +460,7 @@ UDD_IOCTL</h2></td></tr>
</dd>
</dl>
<dl class="section user"><dt>Tags</dt><dd><a class="el" href="group__cobalt__core.html">coreirq-only</a></dd></dl>
<dl class="section note"><dt>Note</dt><dd>In case the ref udd_irq_handler "IRQ handler" from the mini-driver requested the UDD core not to re-enable the interrupt line, the application may later request the unmasking by issuing the UDD_RTIOC_IRQEN ioctl(2) command. Writing a non-zero integer to the device via the write(2) system call has the same effect. </dd></dl>
<dl class="section note"><dt>Note</dt><dd>In case the <a class="el" href="structudd__device.html#udd_irq_handler">IRQ handler</a> from the mini-driver requested the UDD core not to re-enable the interrupt line, the application may later request the unmasking by issuing the UDD_RTIOC_IRQEN ioctl(2) command. Writing a non-zero integer to the device via the write(2) system call has the same effect. </dd></dl>
<p>References <a class="el" href="group__rtdm__sync__event.html#ga1217402b82034b26fe25c26f1e5b32c9">rtdm_event_signal()</a>.</p>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment