Files
lcdproc/docs/lcdproc-user/drivers/lircin.docbook
T

201 lines
4.5 KiB
Plaintext
Raw Normal View History

2006-04-06 07:34:45 +00:00
<sect1 id="lirc">
<title>The lirc Driver</title>
2002-05-28 12:29:44 +00:00
<para>
2007-12-01 18:27:40 +00:00
The <code>lirc</code> driver enables you to use any IR remote control
that works with <package>LIRC</package> to control the LCDproc server
<application>LCDd</application> and/or clients that can handle input.
2002-05-28 12:29:44 +00:00
</para>
2002-05-28 12:29:44 +00:00
<para>
2007-01-01 15:56:26 +00:00
Of course you need a working LIRC setup. Refer to the
<ulink url="http://www.lirc.org">LIRC project</ulink> for more
2002-05-28 12:29:44 +00:00
information on LIRC itself.
</para>
<sect2 id="lirc-install">
<title>Checking Your LIRC Setup</title>
<para>
Basically all you need is a running <application>lircd</application>.
And of course you have to start <application>lircd</application>
as root.
</para>
2002-05-28 12:29:44 +00:00
<para>
Also, make sure that the permission of <filename>/dev/lircd</filename>
are correct.
</para>
</sect2>
2006-04-06 07:34:45 +00:00
<sect2 id="lirc-configure">
<title>Build LCDd with the lirc Driver</title>
2002-05-28 12:29:44 +00:00
<para>
2006-04-06 07:34:45 +00:00
You need to add lirc to the --enable-drivers=... list.
2002-05-28 12:29:44 +00:00
</para>
<para>
Then simply run make.
</para>
</sect2>
<sect2 id="lirc-configuration">
2006-04-06 07:34:45 +00:00
<title>Configure LCDd to Use the lirc Driver</title>
2002-05-28 12:29:44 +00:00
<para>
First of all you need to activate the driver by adding a <code>Driver=lirc</code> line
2002-05-28 12:29:44 +00:00
to your <filename>LCDd.conf</filename>
</para>
<example id="lirc-configuration.example">
2006-04-06 07:34:45 +00:00
<title><filename>LCDd.conf</filename>: Activate the lirc driver</title>
2002-05-28 12:29:44 +00:00
<programlisting>
Driver=mtxorb
Driver=lirc
2002-05-28 12:29:44 +00:00
</programlisting>
</example>
<para>
This activates the <code>mtxorb</code> driver as the output driver
and the <code>lirc</code> driver as the input driver.
2002-05-28 12:29:44 +00:00
</para>
<para>
Then you have to modify the <code>[lirc]</code> section of your
2002-05-28 12:29:44 +00:00
<filename>LCDd.conf</filename>.
</para>
2009-06-11 15:34:41 +00:00
</sect2>
2002-05-28 12:29:44 +00:00
2006-04-05 10:36:58 +00:00
<!-- ## LIRC input driver ## -->
<sect2 id="lirc-config">
<title>Configuration in LCDd.conf</title>
<sect3 id="lirc-config-section">
2006-04-05 10:36:58 +00:00
<title>[lirc]</title>
<variablelist>
<varlistentry>
<term>
<property>lircrc</property> =
<parameter><replaceable>FILENAME</replaceable></parameter>
2006-04-05 10:36:58 +00:00
</term>
<listitem>
<para>
2006-10-06 08:54:50 +00:00
<anchor id="which-lircrc" />
2006-04-05 10:36:58 +00:00
Normally all LIRC clients scan the file <filename>~/.lircrc</filename>.
However, you might want to have a separate file to configure the LCDproc lirc driver only.
2006-04-05 10:36:58 +00:00
</para>
<para>
2006-04-06 07:34:45 +00:00
This option enables you to specify the file you want the lirc driver to scan.
2006-04-05 10:36:58 +00:00
If not given it defaults to <filename>~/.lircrc</filename>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
<property>Prog</property> =
<parameter><replaceable>PROGRAM</replaceable></parameter>
2006-04-05 10:36:58 +00:00
</term>
<listitem>
<para>
2006-10-02 21:35:27 +00:00
All LIRC keys are assigned to a program using the <literal>prog=...</literal>
directive in the lirc configuration file.
2006-04-05 10:36:58 +00:00
</para>
<para>
<replaceable>PROGRAM</replaceable> must be the same as in your lirc
2006-04-05 10:36:58 +00:00
configuration file.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect3>
</sect2>
2002-05-28 12:29:44 +00:00
<sect2 id="lircrc">
<title>Modify Your <filename>~/.lircrc</filename></title>
<para>
As mentioned above you can either modify the <filename>~/.lircrc</filename>
2006-04-06 07:34:45 +00:00
or use a separate file for the lirc LCDproc driver (See
2004-12-31 22:14:29 +00:00
<link linkend="which-lircrc">above</link> for details).
2002-05-28 12:29:44 +00:00
</para>
<para>
No matter which file you use, you have to add at least the following
lines to the file:
</para>
<example id="lircrc.example">
2006-10-02 21:35:27 +00:00
<title><filename>~/.lircrc</filename>: Specify the associations from buttons to keys
2006-04-06 07:34:45 +00:00
for the lirc driver</title>
2002-05-28 12:29:44 +00:00
<programlisting>
2002-05-28 12:29:44 +00:00
begin
prog = lcdd
button = 2
2006-04-05 10:36:58 +00:00
config = Up
2002-05-28 12:29:44 +00:00
end
begin
prog = lcdd
button = 4
2006-04-05 10:36:58 +00:00
config = Left
2002-05-28 12:29:44 +00:00
end
begin
prog = lcdd
button = 6
2006-04-05 10:36:58 +00:00
config = Right
2002-05-28 12:29:44 +00:00
end
begin
prog = lcdd
button = 8
2006-04-05 10:36:58 +00:00
config = Down
end
begin
prog = lcdd
button = 1
config = Escape
end
begin
prog = lcdd
button = 0
config = Enter
2002-05-28 12:29:44 +00:00
end
</programlisting>
</example>
<para>
2007-12-01 18:27:40 +00:00
Which buttons you specify here depends on your remote control and your LIRC configuration.
2006-04-05 10:36:58 +00:00
</para>
<para>
The <literal>config</literal> values need to be one of <literal>Up</literal>,
<literal>Down</literal>, <literal>Left</literal>, <literal>Right</literal>,
<literal>Escape</literal> or <literal>Enter</literal>.
For LCDd's server menu at least the keys <literal>Up</literal>, <literal>Escape</literal>
and <literal>Enter</literal> are necessary.
</para>
<para>
<!-- TODO: is this still true with 0.5 ? -->
2002-05-28 12:29:44 +00:00
Of course you can define other keys. Those keys will not be handled by the
server but sent to a client. Refer to the documentation of the client you want
to use, to find out which keys are necessary for that client.
2002-05-28 12:29:44 +00:00
</para>
</sect2>
</sect1>