#
# $Id: README.MatrixOrbital,v 1.2 2000/03/22 07:33:50 reinelt Exp $
#

This is the README file for the MatrixOrbital display driver for lcd4linux

This driver supports the serial interface alphanumeric display modules by
Matrix Orbital Corporation (http://www.matrixorbital.com).

I could only test it with the LCD2041 model, but I think every other (LCD) model 
should work. These displays are supported:

  LCD0821: 2 lines by  8 characters
  LCD1621: 2 lines by 16 characters
  LCD2021: 2 lines by 20 characters
  LCD2041: 4 lines by 20 characters (tested)
  LCD4021: 2 lines by 40 characters

I could not test the vacuum fluorescent display models, but I think they should work, too.
There are no entries for this models in the driver table (at the bottom of MatrixOrbital.c),
but they could be easily added.

The displays come with an RS-232 and an I2C interface. The driver supports the RS-232 interface
only (because I have no idea how to find the I2C bus on my motherboard). 

Power can be applied either via an external DC power supply, a modified floppy power connector
(be aware that you can destroy your display if you get the pins wrong!) or via the RI (ring) 
signal of the RS-232 port. I choosed the latter, and modified a serial card so that it supplies 
+5V from the ISA bus to this pin (again, be aware that this is dangerous if you connect any other 
serial device to this modified port).

The driver supports vertical, horizontal and split bars (two independent bars in one line),
all bar types can be used simultanously. As the displays only have 8 user-defined characters,
the needed characters to display all the bars must be reduced to 8. This is done by replacing
characters with similar ones. To reduce flicker, a character which is displayed at the moment,
will not be redefined, even if it's not used in this run. Only if the character compaction 
fails, this characters will be redefined, too.

The displays have a GPO (general purpose output), where you can connect a LED or something. 
The driver supports controlling this GPO, but this function is unused by now.


Configuration:

The driver needs/supports the following entries in lcd4linux.conf:

Display: a valid Matrix Orbital Display name (e.g. "LCD2041")
Port: serial device the display is attached to (e.g. /dev/ttyS2)
Speed: the baud rate from the display (configured via jumpers) must match 
       this value. Possible values are 1200, 2400, 9600 and 19200
Contrast: sets the LCD display contrast to a level between 0 (light) 
          and 256 (dark). Default value: 160

934344bec98eb24bbc9d83f42019&amp;showmsg=1&amp;follow=1'>isdb-t</a>/<a href='/dtv-scan-tables.git/log/isdb-t/br-rs-Xangrila?id=0aacef5ed891934344bec98eb24bbc9d83f42019&amp;showmsg=1&amp;follow=1'>br-rs-Xangrila</a> (<a href='/dtv-scan-tables.git/log/isdb-t/br-rs-Xangrila?id=0aacef5ed891934344bec98eb24bbc9d83f42019&amp;showmsg=1'>unfollow</a>)</div><div class='content'><table class='list nowrap'><tr class='nohover'><th class='left'>Age</th><th class='left'>Commit message (<a href='/dtv-scan-tables.git/log/isdb-t/br-rs-Xangrila?id=0aacef5ed891934344bec98eb24bbc9d83f42019&amp;follow=1'>Collapse</a>)</th><th class='left'>Author</th><th class='left'>Files</th><th class='left'>Lines</th></tr>
<tr class='logheader'><td><span title='2016-11-18 22:02:44 +0100'>2016-11-18</span></td><td class='logsubject'><a href='/dtv-scan-tables.git/commit/dvb-t/pl-Krosno_Sucha_Gora?id=9481e7c283d3bad69a0440b26a75ab0d16ccdf68&amp;follow=1'>Rename pl-Krosno_Sucha_Gora with only ASCII characters</a></td><td>Thomas Petazzoni</td><td>1</td><td><span class='deletions'>-0</span>/<span class='insertions'>+0</span></td></tr>
<tr class='nohover-highlight'><td/><td colspan='5' class='logmsg'>
The pl-Krosno_Sucha_Gora file, added in commit
4cb113fd15e562f0629000fcad9f41405595198d, is the only file that
contains non-ASCII characters in the tree. This causes a number of
build issues with other packages that don't necessarily handle very
well non-ASCII file name encodings.

Since no other file in the tree contain non-ASCII characters in their
name, this commit renames pl-Krosno_Sucha_Gora similarly.

Examples of files that are named with only ASCII characters even if
the city name really contains non-ASCII characters:

  - pl-Wroclaw should be written pl-Wrocław
  - se-Laxsjo should be written se-Laxsjö
  - de-Dusseldorf should be written de-Düsseldorf
  - vn-Thaibinh should be written vn-Thái_Bình

Since there is no real standardization on the encoding of file names,
we'd better be safe and use only ASCII characters.

Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;


</td></tr>
<tr class='logheader'><td><span title='2016-11-18 22:00:39 +0100'>2016-11-18</span></td><td class='logsubject'><a href='/dtv-scan-tables.git/commit/dvb-c/cz-UPC?id=4662c86cdfcb7433eb1cada0246b78cb30eb30fe&amp;follow=1'>UPC Česká republika - value adjustment for FEC</a></td><td>Josef Schlehofer</td><td>1</td><td><span class='deletions'>-29</span>/<span class='insertions'>+29</span></td></tr>
<tr class='nohover-highlight'><td/><td colspan='5' class='logmsg'>
From AUTO to 3/5.


</td></tr>