Replace <term><command><arg> with <term><property><parameter> to describe
options in the config file because: * <arg> can only be used within <cmdsynopsis>. * <cmdsynopsis> does not allow text outside <command> and <arg>. * <arg> does not allow decorating elements like <literal> or <emphasis>. This fixes #2803057. Add shortcut entities for commonly used parameters (yes/no, size). Remove Debian patch which is obsoleted by above changes.
This commit is contained in:
mmdolze
@@ -360,7 +360,7 @@ By default, the following keystrokes are generated by the different keys:
|
||||
</table>
|
||||
|
||||
You can change the mapping using the
|
||||
<command>KeyDirect_<replaceable>NUM</replaceable></command>
|
||||
<property>KeyDirect_<replaceable>NUM</replaceable></property>
|
||||
configuration option, where <replaceable>NUM</replaceable>
|
||||
is the subscript to the <literal>X</literal> in the table above.
|
||||
</para>
|
||||
@@ -485,7 +485,7 @@ To be more precise, it assumes this mapping:
|
||||
|
||||
<para>
|
||||
This mapping can be changed using the
|
||||
<command>KeyMatrix_<replaceable>X</replaceable>_<replaceable>Y</replaceable></command>
|
||||
<property>KeyMatrix_<replaceable>X</replaceable>_<replaceable>Y</replaceable></property>
|
||||
configuration option, where <replaceable>X</replaceable> and
|
||||
<replaceable>Y</replaceable> are the subscripts to the respective axes above.
|
||||
</para>
|
||||
@@ -720,9 +720,9 @@ This wiring is originally based on "lcdtext" (by Matthias Prinke).
|
||||
|
||||
<note>
|
||||
<para>
|
||||
The <literal>RW</literal> (pin 5) line of the display decides whether the display receives data from the
|
||||
LPT port, or whether it sends data to the LPT port: if grounded it receives, if High or connected
|
||||
to nothing at all it "sends" (i.e., will not work as intended). So, if you are not sure that
|
||||
The <literal>RW</literal> (pin 5) line of the display decides whether the display receives data from the
|
||||
LPT port, or whether it sends data to the LPT port: if grounded it receives, if High or connected
|
||||
to nothing at all it "sends" (i.e., will not work as intended). So, if you are not sure that
|
||||
you need it otherwise, then connect it to GND. This certainly applies if you have only one display.
|
||||
</para>
|
||||
<para>
|
||||
@@ -1053,9 +1053,9 @@ This type of connection should work with winamp.
|
||||
</table>
|
||||
|
||||
<para>
|
||||
(*) on the RW line of the display: this line decides whether the display receives data from the
|
||||
LPT port, or whether it sends data to the LPT port: if grounded it receives, if High or connected
|
||||
to nothing at all it "sends" (i.e., will not work as intended). So, if you are not sure that
|
||||
(*) on the RW line of the display: this line decides whether the display receives data from the
|
||||
LPT port, or whether it sends data to the LPT port: if grounded it receives, if High or connected
|
||||
to nothing at all it "sends" (i.e., will not work as intended). So, if you are not sure that
|
||||
you need it otherwise, then connect it to GND. This certainly applies if you have only one display.
|
||||
</para>
|
||||
|
||||
@@ -1315,9 +1315,9 @@ The LCD connections are:
|
||||
</table>
|
||||
|
||||
<para>
|
||||
(*) on the RW line of the display: this line decides whether the display receives data from the
|
||||
LPT port, or whether it sends data to the LPT port: if grounded it receives, if High or connected
|
||||
to nothing at all it "sends" (i.e., will not work as intended). So, if you are not sure that
|
||||
(*) on the RW line of the display: this line decides whether the display receives data from the
|
||||
LPT port, or whether it sends data to the LPT port: if grounded it receives, if High or connected
|
||||
to nothing at all it "sends" (i.e., will not work as intended). So, if you are not sure that
|
||||
you need it otherwise, then connect it to GND.
|
||||
</para>
|
||||
|
||||
@@ -1915,7 +1915,7 @@ Please address Matteo Pillon for further information.
|
||||
|
||||
<para>
|
||||
The VDR-Wake module by Frank Jepsen is a serial IO extension module for the
|
||||
famous Linux-based VDR that allows to connect an LCD to it and supports LCDproc.
|
||||
famous Linux-based VDR that allows to connect an LCD to it and supports LCDproc.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -1932,7 +1932,7 @@ See <ulink url="http://www.jepsennet.de/vdr/"></ulink>
|
||||
The Pertelian X2040 includes an HD44780 display with enclosure and USB
|
||||
connection.
|
||||
|
||||
In order to work with <package>LCDproc</package> in Linux you need
|
||||
In order to work with <package>LCDproc</package> in Linux you need
|
||||
the <filename>usbserial.ko</filename> and <filename>ftdi_sio.ko</filename>
|
||||
kernel modules loaded. The display will then be available on a
|
||||
serial port <filename>/dev/ttyUSB<replaceable>x</replaceable></filename>.
|
||||
@@ -1954,7 +1954,7 @@ serial port <filename>/dev/ttyUSB<replaceable>x</replaceable></filename>.
|
||||
The PIC-an-LCD module is also supported. It is not connected to the LPT port
|
||||
but to a serial port, which saves you from a lot of potential problems.
|
||||
To use it, specify the device to which you have connected the module in the
|
||||
config file with the <command>Device</command> setting.
|
||||
config file with the <property>Device</property> setting.
|
||||
The default is <filename>/dev/lcd</filename>.
|
||||
It does not support a keypad nor backlight switching.
|
||||
</para>
|
||||
@@ -2147,7 +2147,7 @@ Refer to <link linkend="hd44780-lcdserializer-burning">burning section</link> in
|
||||
<title>BWCT USB LCD module "bwctusb"</title>
|
||||
|
||||
<para>
|
||||
The BWCT USB LCD module, sold by Bernd Walter Computing Technology
|
||||
The BWCT USB LCD module, sold by Bernd Walter Computing Technology
|
||||
(<ulink url="http://www.bwct.de/lcd.html"></ulink>) is a little board
|
||||
that can be piggy-packed to a HD44780 display and connects that to USB.
|
||||
</para>
|
||||
@@ -2157,7 +2157,7 @@ The board, driven by the <code>bwctusb</code> connection type,
|
||||
does neither support a keypad for input, nor more than one single-controller
|
||||
display, nor does it allow setting the backlight or brightness.
|
||||
But you can set the display's contrast using software
|
||||
(see the <command>Contrast</command> configuration parameter).
|
||||
(see the <property>Contrast</property> configuration parameter).
|
||||
</para>
|
||||
|
||||
<sect4 id="hd44780-bwctusb-config">
|
||||
@@ -2165,7 +2165,7 @@ But you can set the display's contrast using software
|
||||
|
||||
<para>
|
||||
If there is more than one BWCT USB module connected to the system,
|
||||
the <command>SerialNumber</command> configuration parameter allows
|
||||
the <property>SerialNumber</property> configuration parameter allows
|
||||
selecting which display is used in LCDd.
|
||||
</para>
|
||||
|
||||
@@ -2187,7 +2187,7 @@ as well as dual controller displays (required for 4*27 and 4*40).
|
||||
|
||||
<para>
|
||||
It is based upon an Atmel AVR Mega8 CPU with a pure software implementation
|
||||
of the USB protocol for the Atmel AVR microcontroller series.
|
||||
of the USB protocol for the Atmel AVR microcontroller series.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -2199,7 +2199,7 @@ for your own interface e.g. for a graphic LCD.
|
||||
<para>
|
||||
Two keys can be connected to the LCD2USB interface board.
|
||||
They can generate three key events that can be mapped to key names using
|
||||
the <command>DirectKey_1</command> to <command>DirectKey_3</command> commands:
|
||||
the <property>DirectKey_1</property> to <property>DirectKey_3</property> commands:
|
||||
one for each key and the third if the keys are pressed simultaneously.
|
||||
With this 3-key setup, menus can be used (see example below).
|
||||
</para>
|
||||
@@ -2216,9 +2216,9 @@ or those developed by <ulink url="http://www.maltepoeggel.de/index.php?site=sp-l
|
||||
<para>
|
||||
Besides the standard configuration options for <code>hd44780</code> displays, the
|
||||
<code>lcd2usb</code> connection type supports three additional options:
|
||||
<command>Contrast</command> to set the display's contrast,
|
||||
<command>Brightness</command> to set the display's brightness when the backlight is switched on and
|
||||
<command>OffBrightness</command> to set the display's brightness when is backlight is switched off.
|
||||
<property>Contrast</property> to set the display's contrast,
|
||||
<property>Brightness</property> to set the display's brightness when the backlight is switched on and
|
||||
<property>OffBrightness</property> to set the display's brightness when is backlight is switched off.
|
||||
All three options expect a number in the range from <literal>0</literal> to <literal>1000</literal>.
|
||||
</para>
|
||||
|
||||
@@ -2249,9 +2249,9 @@ KeyDirect_3=Escape
|
||||
<tip>
|
||||
<para>
|
||||
In order to make the <code>lcd2usb</code> connection type work with a 2-controller display
|
||||
you may need to set the <command>vSpan</command> config option accordingly.
|
||||
you may need to set the <property>vSpan</property> config option accordingly.
|
||||
</para>
|
||||
</tip>
|
||||
</tip>
|
||||
</sect4>
|
||||
|
||||
</sect3>
|
||||
@@ -2262,17 +2262,17 @@ KeyDirect_3=Escape
|
||||
<title>USS-720 USB-to-IEEE 1284 Bridge (Belkin F5U002) "uss720"</title>
|
||||
|
||||
<para>
|
||||
The USS-720 USB-to-IEEE 1284 Bridge is a fully featured USB to parallel chip that is used
|
||||
in most (but not all) Belkin F5U002 USB Parallel Printer Adapters. Because these adapters are
|
||||
inexpensive and readily available on the second-hand market, they provide an excellent solution
|
||||
for users who want to experiment with a parallel port but only have USB ports on their computers.
|
||||
The USS-720 USB-to-IEEE 1284 Bridge is a fully featured USB to parallel chip that is used
|
||||
in most (but not all) Belkin F5U002 USB Parallel Printer Adapters. Because these adapters are
|
||||
inexpensive and readily available on the second-hand market, they provide an excellent solution
|
||||
for users who want to experiment with a parallel port but only have USB ports on their computers.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Because the chip acts as a parallel port, the driver maintains the same features and wiring as
|
||||
the 8-bit "winamp" driver. However, because most USB Parallel Printer Adapters use a centronics
|
||||
printer connector, be sure to convert the pin numbering of the parallel port pins in the "winamp"
|
||||
wiring to the pin numbering of the centronics port. Many tables are available on the internet
|
||||
Because the chip acts as a parallel port, the driver maintains the same features and wiring as
|
||||
the 8-bit "winamp" driver. However, because most USB Parallel Printer Adapters use a centronics
|
||||
printer connector, be sure to convert the pin numbering of the parallel port pins in the "winamp"
|
||||
wiring to the pin numbering of the centronics port. Many tables are available on the internet
|
||||
that illustrate how the pin numbering differs between the two.
|
||||
</para>
|
||||
|
||||
@@ -2280,15 +2280,15 @@ that illustrate how the pin numbering differs between the two.
|
||||
<title>Special configuration options</title>
|
||||
|
||||
<para>
|
||||
Because several manufacturers used the USS720 chip in their USB Parallel Printer Adapters, the
|
||||
<command>VendorID</command> and <command>ProductID</command> options are configurable in the
|
||||
Because several manufacturers used the USS720 chip in their USB Parallel Printer Adapters, the
|
||||
<property>VendorID</property> and <property>ProductID</property> options are configurable in the
|
||||
<filename>LCDd.conf</filename> file.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
Not all Belkin F5U002 USB Parallel Printer Adapters used the USS720 chip. Look for the dark grey
|
||||
adapters with the removable USB cable for best results.
|
||||
Not all Belkin F5U002 USB Parallel Printer Adapters used the USS720 chip. Look for the dark grey
|
||||
adapters with the removable USB cable for best results.
|
||||
</para>
|
||||
</note>
|
||||
|
||||
@@ -2332,7 +2332,7 @@ port expander there (PCF8574P in this example).
|
||||
+-----|A1 | ___
|
||||
Here: 0x00 | | | +---|___|--o 15 backlight
|
||||
=== | | |c 10R
|
||||
| |12 ___ b|/
|
||||
| |12 ___ b|/
|
||||
|13 P7|-----|___|-----|
|
||||
-|INT | 1k |\
|
||||
| | bc557 |e
|
||||
@@ -2354,7 +2354,7 @@ port expander there (PCF8574P in this example).
|
||||
</figure>
|
||||
|
||||
<sect4 id="hd44780-i2c-config">
|
||||
<title>Configuration</title>
|
||||
<title>Configuration</title>
|
||||
|
||||
<example id="hd44780-i2c-config.example">
|
||||
<title>HD44780: Configuration for I<superscript>2</superscript>C with port expander</title>
|
||||
@@ -2374,15 +2374,15 @@ Keypad=no
|
||||
</example>
|
||||
|
||||
<para>
|
||||
The <command>Device</command> configuration setting denotes the device file
|
||||
The <property>Device</property> configuration setting denotes the device file
|
||||
of your I<superscript>2</superscript>C bus (here <filename>/dev/i2c-0</filename>).
|
||||
You have to load the kernel standard module <filename>i2c-dev.ko</filename> and
|
||||
the bus driver, but <emphasis>no</emphasis> I<superscript>2</superscript>C
|
||||
the bus driver, but <emphasis>no</emphasis> I<superscript>2</superscript>C
|
||||
chip modules (e.g. <filename>pcf8574.ko</filename>)!
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <command>Port</command> config option contains the I<superscript>2</superscript>C
|
||||
The <property>Port</property> config option contains the I<superscript>2</superscript>C
|
||||
address of the I<superscript>2</superscript>C port expander
|
||||
(here 0x20, the PCF8574 from the example above, with all address bits set to <literal>0</literal>).
|
||||
|
||||
@@ -2481,7 +2481,7 @@ is the wiring - instead of connecting the display directly to PC (via serial/par
|
||||
it is connected via ethernet and the communication is done over TCP connection.
|
||||
The main feature is - that to power and control the LCD is needed single UTP cable.
|
||||
To use the driver, specify the device IP address or hostname, on which the ethlcd device
|
||||
is accessible by setting in config file the <command>Device</command> value.
|
||||
is accessible by setting in config file the <property>Device</property> value.
|
||||
The default is <filename>ethlcd</filename>.
|
||||
</para>
|
||||
|
||||
@@ -2539,8 +2539,8 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>Port</command> =
|
||||
<arg choice="plain"><replaceable>PORT</replaceable></arg>
|
||||
<property>Port</property> =
|
||||
<parameter><replaceable>PORT</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
For parallel connections, specify the address of the parallel port the LCD is connected to.
|
||||
@@ -2552,8 +2552,8 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>Device</command> =
|
||||
<arg choice="plain"><replaceable>DEVICE</replaceable></arg>
|
||||
<property>Device</property> =
|
||||
<parameter><replaceable>DEVICE</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
If you are using a serial or I<superscript>2</superscript>C connection,
|
||||
@@ -2566,28 +2566,26 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>ConnectionType</command> =
|
||||
<arg choice="plain">
|
||||
<group choice="req">
|
||||
<arg choice="plain"><literal><emphasis>4bit</emphasis></literal></arg>
|
||||
<arg choice="plain"><literal>8bit</literal></arg>
|
||||
<arg choice="plain"><literal>winamp</literal></arg>
|
||||
<arg choice="plain"><literal>serialLpt</literal></arg>
|
||||
<arg choice="plain"><literal>picanlcd</literal></arg>
|
||||
<arg choice="plain"><literal>lcdserializer</literal></arg>
|
||||
<arg choice="plain"><literal>los-panel</literal></arg>
|
||||
<arg choice="plain"><literal>vdr-lcd</literal></arg>
|
||||
<arg choice="plain"><literal>vdr-wakeup</literal></arg>
|
||||
<arg choice="plain"><literal>pertelian</literal></arg>
|
||||
<arg choice="plain"><literal>bwctusb</literal></arg>
|
||||
<arg choice="plain"><literal>lcd2usb</literal></arg>
|
||||
<arg choice="plain"><literal>lis2</literal></arg>
|
||||
<arg choice="plain"><literal>mplay</literal></arg>
|
||||
<arg choice="plain"><literal>i2c</literal></arg>
|
||||
<arg choice="plain"><literal>ftdi</literal></arg>
|
||||
<arg choice="plain"><literal>usblcd</literal></arg>
|
||||
</group>
|
||||
</arg>
|
||||
<property>ConnectionType</property> =
|
||||
{
|
||||
<emphasis><parameter><literal>4bit</literal></parameter></emphasis> |
|
||||
<parameter><literal>8bit</literal></parameter> |
|
||||
<parameter><literal>winamp</literal></parameter> |
|
||||
<parameter><literal>serialLpt</literal></parameter> |
|
||||
<parameter><literal>picanlcd</literal></parameter> |
|
||||
<parameter><literal>lcdserializer</literal></parameter> |
|
||||
<parameter><literal>los-panel</literal></parameter> |
|
||||
<parameter><literal>vdr-lcd</literal></parameter> |
|
||||
<parameter><literal>vdr-wakeup</literal></parameter> |
|
||||
<parameter><literal>pertelian</literal></parameter> |
|
||||
<parameter><literal>bwctusb</literal></parameter> |
|
||||
<parameter><literal>lcd2usb</literal></parameter> |
|
||||
<parameter><literal>lis2</literal></parameter> |
|
||||
<parameter><literal>mplay</literal></parameter> |
|
||||
<parameter><literal>i2c</literal></parameter> |
|
||||
<parameter><literal>ftdi</literal></parameter> |
|
||||
<parameter><literal>usblcd</literal></parameter>
|
||||
}
|
||||
</term>
|
||||
<listitem>
|
||||
<para>
|
||||
@@ -2602,7 +2600,7 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<!-- parallel -->
|
||||
<!-- parallel -->
|
||||
<row>
|
||||
<entry><literal><link linkend="hd44780-4bit">4bit</link></literal></entry>
|
||||
<entry>4bit Wiring to parallel port(default)</entry>
|
||||
@@ -2619,7 +2617,7 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
<entry><literal><link linkend="hd44780-seriallpt">serialLpt</link></literal></entry>
|
||||
<entry>Serial LPT Wiring</entry>
|
||||
</row>
|
||||
<!-- serial -->
|
||||
<!-- serial -->
|
||||
<row>
|
||||
<entry><literal><link linkend="hd44780-picanlcd">picanlcd</link></literal></entry>
|
||||
<entry>PIC-an-LCD serial device "picanlcd"</entry>
|
||||
@@ -2640,7 +2638,7 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
<entry><literal><link linkend="hd44780-vdr-wakeup">vdr-wakeup</link></literal></entry>
|
||||
<entry>VDR-Wakeup module "vdr-wakeup"</entry>
|
||||
</row>
|
||||
<!-- USB -->
|
||||
<!-- USB -->
|
||||
<row>
|
||||
<entry><literal><link linkend="hd44780-pertelian">pertelian</link></literal></entry>
|
||||
<entry>Pertelian X2040 LCD display (<ulink url="http://pertelian.com/joomla/index.php?option=com_content&task=view&id=43&Itemid=48"></ulink>)</entry>
|
||||
@@ -2669,7 +2667,7 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
<entry><literal><link linkend="hd44780-usblcd">usblcd</link></literal></entry>
|
||||
<entry>USBLCD adapter from Adams IT Services (<ulink url="http://www.usblcd.de/"></ulink>)</entry>
|
||||
</row>
|
||||
<!-- I2C -->
|
||||
<!-- I2C -->
|
||||
<row>
|
||||
<entry><literal><link linkend="hd44780-i2c">i2c</link></literal></entry>
|
||||
<entry>LCD driven by PCF8574(A)/PCA9554(A) connected via I<superscript>2</superscript>C</entry>
|
||||
@@ -2692,8 +2690,8 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>Speed</command> =
|
||||
<arg choice="plain"><replaceable>BITRATE</replaceable></arg>
|
||||
<property>Speed</property> =
|
||||
<parameter><replaceable>BITRATE</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
For a serial connection, set to the serial port bitrate. To use
|
||||
@@ -2703,15 +2701,13 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>CharMap</command> =
|
||||
<arg choice="plain">
|
||||
<group choice="req">
|
||||
<arg choice="plain"><literal><emphasis>hd44780_default</emphasis></literal></arg>
|
||||
<arg choice="plain"><literal>hd44780_euro</literal></arg>
|
||||
<arg choice="plain"><literal>ea_ks0073</literal></arg>
|
||||
<arg choice="plain"><literal>sed12780f_0b</literal></arg>
|
||||
</group>
|
||||
</arg>
|
||||
<property>CharMap</property> =
|
||||
{
|
||||
<emphasis><parameter><literal>hd44780_default</literal></parameter></emphasis> |
|
||||
<parameter><literal>hd44780_euro</literal></parameter> |
|
||||
<parameter><literal>ea_ks0073</literal></parameter> |
|
||||
<parameter><literal>sed12780f_0b</literal></parameter>
|
||||
}
|
||||
</term>
|
||||
<listitem><para>
|
||||
Set the character mapping depending on the display you have:
|
||||
@@ -2719,21 +2715,21 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
<listitem><para>
|
||||
The default, <literal>hd44780_default</literal>, is for "classic"
|
||||
HD44780 displays.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<literal>hd44780_euro</literal> is for displays with a ROM mask
|
||||
supporting the european charset (ROM code A02).
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<literal>ea_ks0073</literal> is the charmap for Electronic
|
||||
Assembly's KS0073 based displays. These devices have a richer
|
||||
charset, including many icons and many more characters of the
|
||||
ISO-8859-1 than standard HD44780s.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<literal>sed12780f_0b</literal> is for some SED 1278 displays.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<literal>sed12780f_0b</literal> is for some SED 1278 displays.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
You only need to set this parameter if you have a non-standard
|
||||
HD44780 display.
|
||||
|
||||
@@ -2749,13 +2745,7 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>Keypad</command> =
|
||||
<arg choice="plain">
|
||||
<group choice="req">
|
||||
<arg choice="plain"><literal>yes</literal></arg>
|
||||
<arg choice="plain"><literal><emphasis>no</emphasis></literal></arg>
|
||||
</group>
|
||||
</arg>
|
||||
<property>Keypad</property> = ¶meters.yesnodef;
|
||||
</term>
|
||||
<listitem><para>
|
||||
Tell whether you have a keypad connected.
|
||||
@@ -2765,8 +2755,8 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>Brightness</command> =
|
||||
<arg choice="plain"><replaceable>BRIGHTNESS</replaceable></arg>
|
||||
<property>Brightness</property> =
|
||||
<parameter><replaceable>BRIGHTNESS</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
Set the initial brightness when the backlight is on
|
||||
@@ -2778,8 +2768,8 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>OffBrightness</command> =
|
||||
<arg choice="plain"><replaceable>BRIGHTNESS</replaceable></arg>
|
||||
<property>OffBrightness</property> =
|
||||
<parameter><replaceable>BRIGHTNESS</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
Set the initial off-brightness, i.e. the brightness when the backlight is off,
|
||||
@@ -2791,8 +2781,8 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>Contrast</command> =
|
||||
<arg choice="plain"><replaceable>CONTRAST</replaceable></arg>
|
||||
<property>Contrast</property> =
|
||||
<parameter><replaceable>CONTRAST</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
Set the initial contrast for the <code>bwctusb</code> and
|
||||
@@ -2808,13 +2798,7 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>Backlight</command> =
|
||||
<arg choice="plain">
|
||||
<group choice="req">
|
||||
<arg choice="plain"><literal>yes</literal></arg>
|
||||
<arg choice="plain"><literal><emphasis>no</emphasis></literal></arg>
|
||||
</group>
|
||||
</arg>
|
||||
<property>Backlight</property> = ¶meters.yesnodef;
|
||||
</term>
|
||||
<listitem><para>
|
||||
Specifiy if you have a switchable backlight.
|
||||
@@ -2823,13 +2807,7 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>OutputPort</command> =
|
||||
<arg choice="plain">
|
||||
<group choice="req">
|
||||
<arg choice="plain"><literal>yes</literal></arg>
|
||||
<arg choice="plain"><literal><emphasis>no</emphasis></literal></arg>
|
||||
</group>
|
||||
</arg>
|
||||
<property>OutputPort</property> = ¶meters.yesnodef;
|
||||
</term>
|
||||
<listitem><para>
|
||||
Tell if you have the additional output port ("bargraph") and you want to
|
||||
@@ -2839,29 +2817,18 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>Lastline</command> =
|
||||
<arg choice="plain">
|
||||
<group choice="req">
|
||||
<arg choice="plain"><literal><emphasis>yes</emphasis></literal></arg>
|
||||
<arg choice="plain"><literal>no</literal></arg>
|
||||
</group>
|
||||
</arg>
|
||||
<property>Lastline</property> = ¶meters.yesdefno;
|
||||
</term>
|
||||
<listitem><para>
|
||||
Specifies whether the lowest pixel line of a character is pixel addressable
|
||||
or if it controls an underline effect.
|
||||
or if it controls an underline effect.
|
||||
The default is <literal>yes</literal>, meaning a pixel addressable last pixel line.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>Size</command> =
|
||||
<arg choice="plain">
|
||||
<replaceable>WIDTH</replaceable>
|
||||
<literal>x</literal>
|
||||
<replaceable>HEIGHT</replaceable>
|
||||
</arg>
|
||||
<property>Size</property> = ¶meters.size;
|
||||
</term>
|
||||
<listitem><para>
|
||||
Specifies the size of the LCD.
|
||||
@@ -2872,11 +2839,11 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>vSpan</command> =
|
||||
<arg choice="plain">
|
||||
<property>vSpan</property> =
|
||||
<parameter>
|
||||
<replaceable>HEIGHT</replaceable>
|
||||
<literal>,</literal>…
|
||||
</arg>
|
||||
</parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
The "vertical span" when using the driver with multi-controller displays
|
||||
@@ -2898,13 +2865,7 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>ExtendedMode</command> =
|
||||
<arg choice="plain">
|
||||
<group choice="req">
|
||||
<arg choice="plain"><literal>yes</literal></arg>
|
||||
<arg choice="plain"><literal><emphasis>no</emphasis></literal></arg>
|
||||
</group>
|
||||
</arg>
|
||||
<property>ExtendedMode</property> = ¶meters.yesnodef;
|
||||
</term>
|
||||
<listitem><para>
|
||||
If you have a KS0073 or an other 'almost HD44780-compatible', set this
|
||||
@@ -2914,8 +2875,8 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>LineAddress</command> =
|
||||
<arg choice="plain"><replaceable>ADDR</replaceable></arg>
|
||||
<property>LineAddress</property> =
|
||||
<parameter><replaceable>ADDR</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
If the next line of your display doesn't start <literal>0x20</literal> higher in
|
||||
@@ -2925,8 +2886,8 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>DelayMult</command> =
|
||||
<arg choice="plain"><replaceable>DELAY</replaceable></arg>
|
||||
<property>DelayMult</property> =
|
||||
<parameter><replaceable>DELAY</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
If your display is slow and cannot keep up with the flow of data from
|
||||
@@ -2938,13 +2899,7 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>DelayBus</command> =
|
||||
<arg choice="plain">
|
||||
<group choice="req">
|
||||
<arg choice="plain"><literal><emphasis>yes</emphasis></literal></arg>
|
||||
<arg choice="plain"><literal>no</literal></arg>
|
||||
</group>
|
||||
</arg>
|
||||
<property>DelayBus</property> = ¶meters.yesdefno;
|
||||
</term>
|
||||
<listitem><para>
|
||||
You can reduce the inserted delays by setting this to <literal>no</literal>.
|
||||
@@ -2955,8 +2910,8 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>KeepAliveDisplay</command> =
|
||||
<arg choice="plain"><replaceable>SECONDS</replaceable></arg>
|
||||
<property>KeepAliveDisplay</property> =
|
||||
<parameter><replaceable>SECONDS</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
Some displays (e.g. <code>vdr-wakeup</code>) need a message from the driver to
|
||||
@@ -2969,8 +2924,8 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>RefreshDisplay</command> =
|
||||
<arg choice="plain"><replaceable>SECONDS</replaceable></arg>
|
||||
<property>RefreshDisplay</property> =
|
||||
<parameter><replaceable>SECONDS</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
If you experience occasional garbage on your display you can use this
|
||||
@@ -2982,12 +2937,12 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>KeyDirect_<replaceable>NUM</replaceable></command> =
|
||||
<arg choice="plain"><replaceable>KEY</replaceable></arg>
|
||||
<property>KeyDirect_<replaceable>NUM</replaceable></property> =
|
||||
<parameter><replaceable>KEY</replaceable></parameter>
|
||||
</term>
|
||||
<term>
|
||||
<command>KeyMatrix_<replaceable>X</replaceable>_<replaceable>Y</replaceable></command> =
|
||||
<arg choice="plain"><replaceable>KEY</replaceable></arg>
|
||||
<property>KeyMatrix_<replaceable>X</replaceable>_<replaceable>Y</replaceable></property> =
|
||||
<parameter><replaceable>KEY</replaceable></parameter>
|
||||
</term>
|
||||
<listitem>
|
||||
<para>
|
||||
@@ -3008,36 +2963,36 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>VendorID</command> =
|
||||
<arg choice="plain"><replaceable>VENDORID</replaceable></arg>
|
||||
<property>VendorID</property> =
|
||||
<parameter><replaceable>VENDORID</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
USB vendor ID to look for in certain USB connection types.
|
||||
When using an FTDI chip with connection type <code>ftdi</code>, the default value is
|
||||
<literal>0x4003</literal>.
|
||||
When using a USS720 chip with connection type <code>uss720</code>, the default value is
|
||||
USB vendor ID to look for in certain USB connection types.
|
||||
When using an FTDI chip with connection type <code>ftdi</code>, the default value is
|
||||
<literal>0x4003</literal>.
|
||||
When using a USS720 chip with connection type <code>uss720</code>, the default value is
|
||||
<literal>0x1293</literal>.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>ProductID</command> =
|
||||
<arg choice="plain"><replaceable>PRODUCTID</replaceable></arg>
|
||||
<property>ProductID</property> =
|
||||
<parameter><replaceable>PRODUCTID</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
USB product ID to look for in certain USB connection types.
|
||||
When using an FTDI chip with connection type <code>ftdi</code>, the default value is
|
||||
USB product ID to look for in certain USB connection types.
|
||||
When using an FTDI chip with connection type <code>ftdi</code>, the default value is
|
||||
<literal>0x6001</literal>.
|
||||
When using a USS720 chip with connection type <code>uss720</code>, the default value is
|
||||
When using a USS720 chip with connection type <code>uss720</code>, the default value is
|
||||
<literal>0x0002</literal>.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>SerialNumber</command> =
|
||||
<arg choice="plain"><replaceable>SERIALNO</replaceable></arg>
|
||||
<property>SerialNumber</property> =
|
||||
<parameter><replaceable>SERIALNO</replaceable></parameter>
|
||||
</term>
|
||||
<listitem><para>
|
||||
Serial number of the USB device to look for with
|
||||
@@ -3052,36 +3007,6 @@ This can be done by specifying <option>--enable-drivers=all</option> or by inclu
|
||||
</sect2>
|
||||
|
||||
|
||||
<!--
|
||||
<sect2 id="hd44780-running">
|
||||
<title>Running</title>
|
||||
|
||||
<para>
|
||||
Modify the <filename>LCDd.conf</filename> file before you run LCDd. In this config file are
|
||||
detailed instructions on how to configure the HD44780 driver.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Then as usual, start LCDd with the correct config file:
|
||||
</para>
|
||||
<para>
|
||||
E.g. <command>LCDd -c ./LCDd.conf</command>
|
||||
</para>
|
||||
<para>
|
||||
If you want to override the driver selection in <filename>LCDd.conf</filename> then use:
|
||||
</para>
|
||||
<para>
|
||||
<command>LCDd -c ./LCDd.conf -d HD44780</command>
|
||||
</para>
|
||||
<para>
|
||||
If you use this, the HD44780 driver will read the options from the config
|
||||
file anyway.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
-->
|
||||
|
||||
|
||||
<sect2 id="hd44780-miscellania">
|
||||
<title>Miscellania</title>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user