Commit d04a78fb authored by Gilles Chanteperdrix's avatar Gilles Chanteperdrix
Browse files

doc: regenerate

parent c5da78a1
Installing Xenomai 2.6.4
Installing Xenomai 2.6.5
-------------------------------------------------------------------------------
......
......@@ -62,6 +62,8 @@ Table of Contents
6.4. Any Xenomai service fails with code -38 (ENOSYS)
6.5. My application reserves a lot of memory
-------------------------------------------------------------------------------
This file is a troubleshooting guide about various known issues regarding
Xenomai.
......@@ -73,6 +75,8 @@ For questions, corrections and improvements, write to the mailing list:
1. Kernel configuration
-----------------------
When configuring the Linux kernel, some options should be avoided.
CONFIG_CPU_FREQ
......@@ -96,6 +100,8 @@ For x86 specific options see also this page:
2. Xenomai or I-pipe error in the kernel log
--------------------------------------------
If the Xenomai and I-pipe messages do not appear in the kernel log as:
I-pipe: head domain Xenomai registered.
......@@ -111,7 +117,9 @@ Xenomai: starting RTDM services.
Where <arch> is the architecture you use, check the following sections, they
describe the usual error messages you may encounter.
2.1. Kernel stops after "Uncompressing Linux… done, booting the kernel."
------------------------------------------------------------------------
This means that the kernel crashes before the console is enabled. You should
enable the CONFIG_EARLY_PRINTK option. For some architectures (blackfin, x86,
......@@ -122,27 +130,35 @@ values.
For the ARM architecture, you have to enable CONFIG_DEBUG_KERNEL and
CONFIG_DEBUG_LL in order to be able to enable CONFIG_EARLY_PRINTK.
2.2. Kernel stops with an OOPS
------------------------------
Please make sure that you have followed the "Kernel configuration" section.
Then, try capturing the oops text (using a serial console or netconsole) post
the oops to the xenomai mailing list: "xenomai@xenomai.org", with the kernel
configuration you used to compile the failing kernel.
2.3. Kernel boots but does not print any message
------------------------------------------------
Your distribution may be configured to pass the quiet option on the kernel
command line. In this case, the kernel does not print all the log messages,
however, they are still available using the dmesg command.
2.4. Xenomai: compiled for TSC, but CPU has no TSC
--------------------------------------------------
You selected a CPU which as a TSC ("Pentium classic", and above), but the CPU
on which you run the kernel has no TSC. This issue was resolved in the I-pipe
core for Linux 3.4, but for prior versions, you need to select a CPU without a
TSC when configuring the kernel, and recompile the kernel.
2.5. Xenomai has detected a CPU frequency of 0
----------------------------------------------
This happens when running in emulators. In such a case, Xenomai can not run as
it needs to know the clock frequency.
......@@ -151,15 +167,21 @@ This may also happen when using I-pipe core patch for Linux 3.2, compiled for a
CPU with a TSC, but running on a CPU without a TSC, as in the "Xenomai:
compiled for TSC case.
2.6. I-pipe: could not find timer for cpu #x
--------------------------------------------
See code -19.
2.7. Xenomai: Local APIC absent or disabled!
--------------------------------------------
See code -19.
2.8. Xenomai: SMI-enabled chipset found, but SMI workaround disabled
--------------------------------------------------------------------
First you should run the latency test under some load and see if you experience
any pathological latency ("pathological" meaning more than, say, 100
......@@ -210,14 +232,18 @@ when running the latency test again, your peripheral is working properly and
you still observe high latencies, then you are out of luck, the peripheral you
want is likely to be the cause of such latencies.
2.9. Xenomai: system init failed, code -19
------------------------------------------
The most probable reason is that Xenomai could not find a timer.
Check that you have not enabled one of the options in the "Kernel
configuration" section.
2.9.1. On x86
-------------
You will most likely also see the following message:
......@@ -238,7 +264,9 @@ support is available. There are two options for fixing this issue:
You may want to look at the file Documentation/kernel-parameters.txt from
the Linux source tree, for more information about this parameter.
2.9.2. On AMD x86_64
--------------------
You will most likely also see the following message:
......@@ -253,7 +281,9 @@ located in the Advanced BIOS Features→ menu (AMD C1E Support).
Disabling AMD K8 Cool&Quiet option in a BIOS does not solve the
problem.
2.9.3. On ARM
-------------
If you see the following message:
......@@ -264,7 +294,9 @@ configuration, but the processor on which you are running the kernel has no
support for VFP. In that case, you have to recompile the kernel with
CONFIG_XENO_HW_FPU disabled.
2.9.4. On other supported platforms
-----------------------------------
As on x86, on other platforms where Xenomai shares the timer with Linux, the
timer is only used if it was not shut down by Linux. So you should check the
......@@ -278,7 +310,9 @@ post a message to the xenomai mailing list: "xenomai@xenomai.org", sending:
issue
* the complete kernel boot log.
2.9.5. On a new I-pipe port
---------------------------
You will most likely also see the following message:
......@@ -292,7 +326,9 @@ with the ipipe_timer member of the struct clock_event_device structure.
For an example on the ARM platform see this page:
"http://www.xenomai.org/index.php/I-pipe-core:ArmPorting#The_general_case".
2.10. Xenomai: system init failed, code -22
-------------------------------------------
On the ppc64 platform, check whether CONFIG_PPC_64K_PAGES is defined in your
kernel configuration. If so, then you likely need to raise all Xenomai
......@@ -304,11 +340,15 @@ assumption that PAGE_SIZE = 4k.
3. Problems when running the latency test
-----------------------------------------
The first test to run to see if Xenomai is running correctly on your platform
is the latency test. The following sections describe the usual reasons for this
test not to run correctly.
3.1. Xenomai: binding failed: Operation not permitted
-----------------------------------------------------
This error message means that you are trying to run the latency test as a
non-root user. Using Xenomai services requires root privileges (more precisely
......@@ -316,7 +356,9 @@ CAP_SYS_NICE). However, you can allow a specific group to access Xenomai
services, by following the instructions on this page:
"http://xenomai.org/index.php/Non-root_RT".
3.2. Xenomai: --enable-x86-sep needs NPTL and Linux 2.6.x or higher
-------------------------------------------------------------------
On the x86 architecture, the configure script option --enable-x86-sep allows
Xenomai to use the SYSENTER/SYSEXIT mechanism for issuing system calls.
......@@ -325,16 +367,22 @@ However, this mechanism requires support from the libc. Currently, we know the
glibc with NPTL has this support, other libraries will cause Xenomai
applications to fail with this error message.
3.3. latency: failed to open benchmark device
---------------------------------------------
You have launched latency -t 1 or latency -t 2 which both require the kernel to
have been compiled with the CONFIG_XENO_DRIVERS_TIMERBENCH option enabled.
3.4. Hardware tsc is not a fast wrapping one
--------------------------------------------
See the "ARM tsc emulation issues" section.
3.5. Xenomai: incompatible ABI revision level
---------------------------------------------
Each Xenomai branch (2.1, 2.2, 2.3, 2.4, 2.5, 2.6,…) defines a kernel/user ABI,
so that it is possible to mix kernels and user-space supports of different
......@@ -355,7 +403,9 @@ package.
If you compiled and installed the correct Xenomai user-space support, there are
probably files on your system remaining from a previous installation.
3.6. Xenomai: incompatible feature set
--------------------------------------
Since kernel-space support and user-space support are compiled separately, each
Xenomai application checks, at startup, whether the kernel and user-space
......@@ -363,18 +413,24 @@ supports have been configured with compatible options. If you see this message,
it means they have not. See README.INSTALL for further details. The following
sections detail the most frequent reasons for this message.
3.6.1. missing="kuser_tsc"
--------------------------
See the "ARM tsc emulation issues" section.
3.6.2. missing="sep"
--------------------
On the x86 architecture, the configure script option --enable-x86-sep allows
Xenomai to use the SYSENTER/SYSEXIT mechanism for issuing system calls.
However, this mechanism requires a recent kernel (2.6 or higher).
3.6.3. missing="smp/nosmp"
--------------------------
On some SMP-capable architectures, for kernel-space and user-space supports to
be compatible, both should be compiled with the same setting for SMP.
......@@ -389,7 +445,9 @@ Other SMP-capable architectures may run userland code built with --enable-smp
or --disable-smp over the same kernel indifferently, at no noticeable
performance cost. These architectures never receive such SMP-related error.
3.6.4. missing="tsc"
--------------------
This error is specific to the x86 architecture. You enabled tsc in user-space
by passing the --enable-x86-tsc option, but you selected a processor when
......@@ -403,11 +461,15 @@ and recompile it.
If your processor does not have a tsc, you should not pass the --enable-x86-tsc
option to the configure script.
3.7. Xenomai: kernel/user tsc emulation mismatch
------------------------------------------------
See the "ARM tsc emulation issues" section.
3.8. Xenomai: native skin or CONFIG_XENO_OPT_PERVASIVE disabled
---------------------------------------------------------------
Possible reasons for this error are:
......@@ -421,7 +483,9 @@ Possible reasons for this error are:
* you are trying to run Xenomai user-space support compiled for x86_32 on an
x86_64 kernel.
3.9. latency: not found
-----------------------
On the ARM platform this message happens when there is a mismatch between
kernel and user for the EABI setting: for instance you compiled the user-space
......@@ -430,24 +494,32 @@ on a kernel with CONFIG_AEABI but without CONFIG_OABI_COMPAT. Or vice versa,
when running user-space compiled with an EABI toolchain on a kernel without
CONFIG_AEABI.
3.10. Xenomai: watchdog triggered (period too short?)
-----------------------------------------------------
Xenomai watchdog has stopped the latency test because it was using all the CPU
in primary mode. This is likely due to a too short period, re-run the latency
test passing a longer period using the -p option.
3.11. Xenomai: Your board/configuration does not allow tsc emulation
--------------------------------------------------------------------
See the "ARM tsc emulation issues" section.
3.12. the latency test hangs
----------------------------
The most common reason for this issues is a too short period passed with the -p
option, try increasing the period. If you enable the watchdog (option
CONFIG_XENO_OPT_WATCHDOG, in your kernel configuration), you should see the
"Xenomai: watchdog triggered (period too short?)" message.
3.13. the latency test shows high latencies
-------------------------------------------
The latency test runs, but you are seeing high latencies.
......@@ -481,7 +553,9 @@ following line to the Device section:
Option "NoAccel"
3.14. ARM tsc emulation issues
------------------------------
In order to allow applications to measure short durations with as little
overhead as possible, Xenomai uses a 64 bits high resolution counter. On x86,
......@@ -550,10 +624,14 @@ configuration, should be configured to large enough values. Try increasing them
and recompiling the kernel.
5. Known Bugs and Limitations
-----------------------------
5.1. 2.6.2/x86
--------------
2.6.2 (like any previous Xenomai release) does not handle the extended
5. Known Bugs and Limitations
processor state (xsave/xrstor) yet.
2.6.2 automatically disables this CPU feature at boot when the host kernel
......@@ -567,9 +645,13 @@ when the switchtest program runs in the background, due to incorrect FPU
management in real-time mode.
6. Problem with my code (not Xenomai code)
------------------------------------------
6.1. "Warning: <service> is deprecated" while compiling kernel code
-------------------------------------------------------------------
6. Problem with my code (not Xenomai code)
Where <service> is a thread creation service, one of:
* cre_tsk
......@@ -593,7 +675,9 @@ You may switch those warnings off by enabling the
CONFIG_XENO_OPT_NOWARN_DEPRECATED option in your kernel configuration, but
nevertheless, you have been WARNED.
6.2. "Xenomai: process memory not locked (missing mlockall?)" at startup
------------------------------------------------------------------------
In order to avoid unwanted transitions to secondary domain, an application
using Xenomai services should call, before any Xenomai service:
......@@ -614,7 +698,9 @@ with the configure script.
See configure --help.
6.3. High latencies when transitioning from primary to secondary mode
---------------------------------------------------------------------
Such transition requires to wake up the Linux task underlying your real-time
thread when running in secondary mode, since the latter needs to leave the
......@@ -653,7 +739,9 @@ granularity improves at each new release, there are still a few catches:
in the Xenomai domain, and activities from such domain can preempt any
activity from the Linux domain, including disk drivers.
6.4. Any Xenomai service fails with code -38 (ENOSYS)
-----------------------------------------------------
Possible reasons for this error are:
......@@ -667,7 +755,9 @@ Possible reasons for this error are:
* you are trying to run Xenomai user-space support compiled for x86_32 on an
x86_64 kernel.
6.5. My application reserves a lot of memory
--------------------------------------------
Your user-space application unexpectedly reserves a lot of virtual memory, as
reported by "top" or /proc/<pid>/maps. Sometimes OOM situations even appear
......
......@@ -3,6 +3,7 @@
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.5"/>
<title>Xenomai API: ksrc/drivers/analogy/intel/8255.c File Reference</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
......@@ -12,6 +13,7 @@
<script type="text/javascript" src="navtree.js"></script>
<script type="text/javascript">
$(document).ready(initResizable);
$(window).load(resizeHeight);
</script>
<link href="search/search.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="search/search.js"></script>
......@@ -31,7 +33,7 @@
<tr style="height: 56px;">
<td style="padding-left: 0.5em;">
<div id="projectname">Xenomai API
&#160;<span id="projectnumber">2.6.4</span>
&#160;<span id="projectnumber">2.6.5</span>
</div>
</td>
</tr>
......@@ -39,7 +41,7 @@
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.1.2 -->
<!-- Generated by Doxygen 1.8.5 -->
<script type="text/javascript">
var searchBox = new SearchBox("searchBox", "search",false,'Search');
</script>
......@@ -94,14 +96,11 @@ $(document).ready(function(){initNavTree('8255_8c.html','');});
<p>Analogy subdevice driver for 8255 chip.
<a href="#details">More...</a></p>
<div class="textblock"><div class="dynheader">
Include dependency graph for 8255.c:</div>
<div class="dyncontent">
<div class="center"><img src="8255_8c__incl.png" border="0" usemap="#ksrc_2drivers_2analogy_2intel_28255_8c" alt=""/></div>
<map name="ksrc_2drivers_2analogy_2intel_28255_8c" id="ksrc_2drivers_2analogy_2intel_28255_8c">
<area shape="rect" id="node7" href="analogy__driver_8h.html" title="Analogy for Linux, driver facilities." alt="" coords="220,179,385,208"/><area shape="rect" id="node15" href="8255_8h.html" title="Hardware driver for 8255 chip." alt="" coords="307,101,368,131"/><area shape="rect" id="node9" href="os__facilities_8h.html" title="Analogy for Linux, Operation system facilities." alt="" coords="67,256,216,285"/><area shape="rect" id="node11" href="context_8h.html" title="Analogy for Linux, context structure / macros declarations." alt="" coords="240,256,365,285"/><area shape="rect" id="node13" href="device_8h.html" title="Analogy for Linux, device related features." alt="" coords="389,256,509,285"/></map>
</div>
</div><a name="details" id="details"></a><h2>Detailed Description</h2>
<div class="textblock"><code>#include &lt;linux/module.h&gt;</code><br/>
<code>#include &lt;linux/ioport.h&gt;</code><br/>
<code>#include &lt;<a class="el" href="analogy__driver_8h_source.html">analogy/analogy_driver.h</a>&gt;</code><br/>
<code>#include &quot;<a class="el" href="8255_8h_source.html">8255.h</a>&quot;</code><br/>
</div><a name="details" id="details"></a><h2 class="groupheader">Detailed Description</h2>
<div class="textblock"><p>Analogy subdevice driver for 8255 chip. </p>
<dl class="section note"><dt>Note</dt><dd>Copyright (C) 1999 David A. Schleef <a href="#" onclick="location.href='mai'+'lto:'+'ds@'+'sc'+'hle'+'ef'+'.or'+'g'; return false;">ds@sc<span style="display: none;">.nosp@m.</span>hlee<span style="display: none;">.nosp@m.</span>f.org</a></dd></dl>
<p>This code is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.</p>
......@@ -113,9 +112,9 @@ Include dependency graph for 8255.c:</div>
<div id="nav-path" class="navpath"><!-- id is needed for treeview function! -->
<ul>
<li class="navelem"><a class="el" href="dir_9e8a34f81d280d0a8a8168d1682661d5.html">ksrc</a></li><li class="navelem"><a class="el" href="dir_c06c82651d85993ad77af8b2ed61e563.html">drivers</a></li><li class="navelem"><a class="el" href="dir_6251052e634d91598970e002c1aeb0fd.html">analogy</a></li><li class="navelem"><a class="el" href="dir_b7a55bf7bd5ed5a192e77b717b3729f1.html">intel</a></li><li class="navelem"><a class="el" href="8255_8c.html">8255.c</a></li>
<li class="footer">Generated on Wed Sep 24 2014 22:53:24 for Xenomai API by
<li class="footer">Generated on Thu Jul 7 2016 13:24:59 for Xenomai API by
<a href="http://www.doxygen.org/index.html">
<img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.8.1.2 </li>
<img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.8.5 </li>
</ul>
</div>
</body>
......
var 8255_8c =
[
[ "CALLBACK_ARG", "8255_8c.html#aca43fdf8bf1d83d41304bffcf6f1b1d5", null ],
[ "CALLBACK_FUNC", "8255_8c.html#a80abdff77f2ddc3c10167eb110942f99", null ],
[ "a4l_subdev_8255_init", "8255_8c.html#a0455f6108516ab78df980f9772d18d30", null ],
[ "a4l_subdev_8255_interrupt", "8255_8c.html#ab1321d79125845a8bd09af042bf45d7e", null ],
[ "dev_8255_attach", "8255_8c.html#ac2862d71afa2968122a4c1e81edcc502", null ],
[ "dev_8255_detach", "8255_8c.html#a6570457da8b846ad83979c975d37d981", null ],
[ "do_config", "8255_8c.html#a3a64bb3aa2a16dfe0b0838cb60a67469", null ],
[ "drv_8255_cleanup", "8255_8c.html#ab1958fd5ff50818ee340e5c2389418c9", null ],
[ "drv_8255_init", "8255_8c.html#a9abd7c57455ea3facf3c3a71cc4ea4fc", null ],
[ "EXPORT_SYMBOL_GPL", "8255_8c.html#a3b2a80a72226443c3a755a54068aa7fa", null ],
[ "EXPORT_SYMBOL_GPL", "8255_8c.html#a7c8e61a85eea755d53a6c304cc0ad9ad", null ],
[ "MODULE_DESCRIPTION", "8255_8c.html#a35db8f5402e5e53356cf3d424e915907", null ],
[ "module_exit", "8255_8c.html#a1238242d88c2931f2e6bb2aeb00b4e81", null ],
[ "module_init", "8255_8c.html#aa60ff58e95f01f3d9511a2935f4ca253", null ],
[ "MODULE_LICENSE", "8255_8c.html#ad94b36675e7eb067ea3ce6ff9e244a44", null ],
[ "subd_8255_cancel", "8255_8c.html#a1aa03a8eb0cd046bc2215afa84bc01ed", null ],
[ "subd_8255_cmd", "8255_8c.html#aff04b0265aa6863c939fb8b83650a8ac", null ],
[ "subd_8255_cmdtest", "8255_8c.html#a39e014f878f98f26ced2f5582106cb72", null ],
[ "subd_8255_insn_bits", "8255_8c.html#a3a4ef2caf3a29f32b67250246bc846b1", null ],
[ "subd_8255_insn_config", "8255_8c.html#a455c2057ca0b56f3d470387745b16108", null ],
[ "subdev_8255_cb", "8255_8c.html#a292ee51c80edc8e66f5bc1c52d944b6b", null ],
[ "chandesc_8255", "8255_8c.html#aaf1dbf1c1281a9178f9b413a061fb622", null ],
[ "cmd_mask_8255", "8255_8c.html#aa1689c8601c95a585fbe7ca56a9ca1e0", null ],
[ "drv_8255", "8255_8c.html#a0e62ca38c21b4cdb7c69c1688bc726ca", null ]
];
\ No newline at end of file
<map id="ksrc/drivers/analogy/intel/8255.c" name="ksrc/drivers/analogy/intel/8255.c">
<area shape="rect" id="node7" href="$analogy__driver_8h.html" title="Analogy for Linux, driver facilities." alt="" coords="220,179,385,208"/>
<area shape="rect" id="node15" href="$8255_8h.html" title="Hardware driver for 8255 chip." alt="" coords="307,101,368,131"/>
<area shape="rect" id="node9" href="$os__facilities_8h.html" title="Analogy for Linux, Operation system facilities." alt="" coords="67,256,216,285"/>
<area shape="rect" id="node11" href="$context_8h.html" title="Analogy for Linux, context structure / macros declarations." alt="" coords="240,256,365,285"/>
<area shape="rect" id="node13" href="$device_8h.html" title="Analogy for Linux, device related features." alt="" coords="389,256,509,285"/>
</map>
e5fde04cd8a8aa4eda4ecabaad85feb6
\ No newline at end of file
......@@ -3,6 +3,7 @@
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.5"/>
<title>Xenomai API: ksrc/drivers/analogy/intel/8255.h File Reference</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
......@@ -12,6 +13,7 @@
<script type="text/javascript" src="navtree.js"></script>
<script type="text/javascript">
$(document).ready(initResizable);
$(window).load(resizeHeight);
</script>
<link href="search/search.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="search/search.js"></script>
......@@ -31,7 +33,7 @@
<tr style="height: 56px;">
<td style="padding-left: 0.5em;">
<div id="projectname">Xenomai API
&#160;<span id="projectnumber">2.6.4</span>
&#160;<span id="projectnumber">2.6.5</span>
</div>
</td>
</tr>
......@@ -39,7 +41,7 @@
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.1.2 -->
<!-- Generated by Doxygen 1.8.5 -->
<script type="text/javascript">
var searchBox = new SearchBox("searchBox", "search",false,'Search');
</script>
......@@ -94,23 +96,10 @@ $(document).ready(function(){initNavTree('8255_8h.html','');});
<p>Hardware driver for 8255 chip.
<a href="#details">More...</a></p>
<div class="textblock"><div class="dynheader">
Include dependency graph for 8255.h:</div>
<div class="dyncontent">
<div class="center"><img src="8255_8h__incl.png" border="0" usemap="#ksrc_2drivers_2analogy_2intel_28255_8h" alt=""/></div>
<map name="ksrc_2drivers_2analogy_2intel_28255_8h" id="ksrc_2drivers_2analogy_2intel_28255_8h">
<area shape="rect" id="node3" href="analogy__driver_8h.html" title="Analogy for Linux, driver facilities." alt="" coords="159,101,324,131"/><area shape="rect" id="node5" href="os__facilities_8h.html" title="Analogy for Linux, Operation system facilities." alt="" coords="5,179,155,208"/><area shape="rect" id="node7" href="context_8h.html" title="Analogy for Linux, context structure / macros declarations." alt="" coords="179,179,304,208"/><area shape="rect" id="node9" href="device_8h.html" title="Analogy for Linux, device related features." alt="" coords="328,179,448,208"/></map>
</div>
</div><div class="textblock"><div class="dynheader">
This graph shows which files directly or indirectly include this file:</div>
<div class="dyncontent">
<div class="center"><img src="8255_8h__dep__incl.png" border="0" usemap="#ksrc_2drivers_2analogy_2intel_28255_8hdep" alt=""/></div>
<map name="ksrc_2drivers_2analogy_2intel_28255_8hdep" id="ksrc_2drivers_2analogy_2intel_28255_8hdep">
<area shape="rect" id="node3" href="8255_8c.html" title="Analogy subdevice driver for 8255 chip." alt="" coords="5,110,144,157"/><area shape="rect" id="node5" href="mio__common_8c.html" title="Hardware driver for DAQ&#45;STC based boards." alt="" coords="168,101,315,165"/><area shape="rect" id="node7" href="pcimio_8c.html" title="Hardware driver for NI PCI&#45;MIO E series cards." alt="" coords="339,101,485,165"/></map>
</div>
<div class="textblock"><code>#include &lt;<a class="el" href="analogy__driver_8h_source.html">analogy/analogy_driver.h</a>&gt;</code><br/>
</div>
<p><a href="8255_8h_source.html">Go to the source code of this file.</a></p>
<a name="details" id="details"></a><h2>Detailed Description</h2>
<a name="details" id="details"></a><h2 class="groupheader">Detailed Description</h2>
<div class="textblock"><p>Hardware driver for 8255 chip. </p>
<dl class="section note"><dt>Note</dt><dd>Copyright (C) 1999 David A. Schleef <a href="#" onclick="location.href='mai'+'lto:'+'ds@'+'sc'+'hle'+'ef'+'.or'+'g'; return false;">ds@sc<span style="display: none;">.nosp@m.</span>hlee<span style="display: none;">.nosp@m.</span>f.org</a></dd></dl>
<p>This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.</p>
......@@ -122,9 +111,9 @@ This graph shows which files directly or indirectly include this file:</div>
<div id="nav-path" class="navpath"><!-- id is needed for treeview function! -->
<ul>
<li class="navelem"><a class="el" href="dir_9e8a34f81d280d0a8a8168d1682661d5.html">ksrc</a></li><li class="navelem"><a class="el" href="dir_c06c82651d85993ad77af8b2ed61e563.html">drivers</a></li><li class="navelem"><a class="el" href="dir_6251052e634d91598970e002c1aeb0fd.html">analogy</a></li><li class="navelem"><a class="el" href="dir_b7a55bf7bd5ed5a192e77b717b3729f1.html">intel</a></li><li class="navelem"><a class="el" href="8255_8h.html">8255.h</a></li>
<li class="footer">Generated on Wed Sep 24 2014 22:53:24 for Xenomai API by
<li class="footer">Generated on Thu Jul 7 2016 13:24:59 for Xenomai API by
<a href="http://www.doxygen.org/index.html">
<img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.8.1.2 </li>
<img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.8.5 </li>
</ul>
</div>
</body>
......
var 8255_8h =
[
[ "a4l_subdev_8255_init", "8255_8h.html#ac15e9c82ed05012ee4fd976be9ff2242", null ],
[ "a4l_subdev_8255_interrupt", "8255_8h.html#af102ec7937a0148e62dfcd8999950ff7", null ],
[ "a4l_8255_cb_t", "8255_8h.html#a06038a11f027cf019a8cf2dc847a95c5", null ],
[ "subd_8255_t", "8255_8h.html#a3a6790d315c7d99a9a8d57b0ee6866b4", null ]
];
\ No newline at end of file
<map id="ksrc/drivers/analogy/intel/8255.h" name="ksrc/drivers/analogy/intel/8255.h">
<area shape="rect" id="node3" href="$8255_8c.html" title="Analogy subdevice driver for 8255 chip." alt="" coords="5,110,144,157"/>
<area shape="rect" id="node5" href="$mio__common_8c.html" title="Hardware driver for DAQ&#45;STC based boards." alt="" coords="168,101,315,165"/>
<area shape="rect" id="node7" href="$pcimio_8c.html" title="Hardware driver for NI PCI&#45;MIO E series cards." alt="" coords="339,101,485,165"/>
</map>
c2fa50697aa948b0ae2faa1dc0429683
\ No newline at end of file
<map id="ksrc/drivers/analogy/intel/8255.h" name="ksrc/drivers/analogy/intel/8255.h">
<area shape="rect" id="node3" href="$analogy__driver_8h.html" title="Analogy for Linux, driver facilities." alt="" coords="159,101,324,131"/>
<area shape="rect" id="node5" href="$os__facilities_8h.html" title="Analogy for Linux, Operation system facilities." alt="" coords="5,179,155,208"/>
<area shape="rect" id="node7" href="$context_8h.html" title="Analogy for Linux, context structure / macros declarations." alt="" coords="179,179,304,208"/>
<area shape="rect" id="node9" href="$device_8h.html" title="Analogy for Linux, device related features." alt="" coords="328,179,448,208"/>
</map>
5649b26c90e32678eb1cad473b2be3f6
\ No newline at end of file
......@@ -3,6 +3,7 @@
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.5"/>
<title>Xenomai API: ksrc/drivers/analogy/intel/8255.h Source File</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
......@@ -12,6 +13,7 @@
<script type="text/javascript" src="navtree.js"></script>
<script type="text/javascript">
$(document).ready(initResizable);
$(window).load(resizeHeight);
</script>
<link href="search/search.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="search/search.js"></script>
......@@ -31,7 +33,7 @@
<tr style="height: 56px;">
<td style="padding-left: 0.5em;">
<div id="projectname">Xenomai API
&#160;<span id="projectnumber">2.6.4</span>
&#160;<span id="projectnumber">2.6.5</span>
</div>
</td>
</tr>
......@@ -39,7 +41,7 @@
</table>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.1.2 -->
<!-- Generated by Doxygen 1.8.5 -->
<script type="text/javascript">
var searchBox = new SearchBox("searchBox", "search",false,'Search');