<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<TITLE>LIRC - Linux Infrared Remote Control</TITLE>
<LINK REL="stylesheet" TYPE="text/css" HREF="lirc.css">
<LINK REL="shortcut icon" HREF="../images/favicon.ico">
<META NAME="description" CONTENT="LIRC - Linux Infrared Remote Control">
<META NAME="keywords" CONTENT="linux remote control, multimedia">
<META charset="UTF-8">
</HEAD>
<body>
<TABLE CLASS="menu"><TR>
<TD CLASS="menu"><IMG class="menuimg" SRC="../images/diode.gif" ALT="LIRC icon" ALIGN="LEFT"></TD>
<TD><IMG class="menuimg" SRC="../images/lirc.gif" ALT="LIRC logo" ALIGN="RIGHT"></TD>
</TR></TABLE>
<center><h1>Default driver.</h1></center>
<p>
</p>
<p>
The default driver reads/writes data to the <code>/dev/lirc[0-9]</code>
devices. It's a LIRC_LIRCMODE2 type driver handling timing information.</p>
<p>
</p>
<p>
The <code>/dev/lirc[0-9]</code> devices are created by certain kernel
modules (most of which former LIRC drivers which have been moved into
the kernel). They reflect a IR remote driver loaded by the kernel.</p>
<p>
</p>
<p>
The kernel drivers will by default recieve and decode the timing data
from the remote and send them as events on a /dev/input device. However,
the will also make the raw timing data available on a /dev/lirc device.
The default driver listens to this data, and decodes it to events
presented to the applications on a (default)<code> /var/run/lirc/lircd
</code> socket.
</p>
<p>
Without further configuration, this means that a single button press can
reach the application both on the /dev/input and the /var/run/lirc/lircd
interfaces. The symptoms of this is that each press is doubled. </p>
<p>
</p>
<p>
To fix this, force the kernel driver to use the lirc protocol, which
effectively mutes the /dev/input device. On a simple system with only
one remote this is done using
</p>
<pre>
sudo echo 'lirc' > /sys/class/rc/rc0/protocols
</pre>
<p>
From 0.9.3+ this is done automatically by the driver.
</p>
<p>
The driver also supports sending (IR blasting).
</p>
<p>
Contrary to most drivers, the default driver probes the loaded kernel
modules about their capabilities. This means that the static capability
information displayed by lirc-lsplugins(1) doesn't make much sense.
</p>
<p class="footer">
[<A HREF="http://www.lirc.org/">LIRC homepage</A>]
</p>
</body>
</html>
