#
# $Id: README.Drivers,v 1.4 2001/03/09 13:08:11 ltoetsch Exp $
#

How to write new display drivers for lcd4linux

If you plan to write a new display driver for lcd4linux, you should follow
this guidelines:

* use Skeleton.c as a start point.
  You might also have a look at Text.c

* create a new sourcefile <drivername>.c and add it to the bottom of
  Makefile.am

* add an entry to configure.in

* there's no need for a <drivername>.h

* create one (or more) unique display names (your driver will be selected by
  this name in the 'Display'-line of lcd4linux.conf).

* include "display.h" in your driver, to get the LCD structure and various 
  BAR_ definitions

* include "cfg.h" if you need to access settings in the config file.

* create a LCD table at the bottom of your driver, and fill it with the
  appropriate values. Take care that you specify the correct bar capabilities
  of your display or driver:

  BAR_L:  horizontal bars headed left
  BAR_R:  horizontal bars headed right
  BAR_H2: driver supports horizontal dual-bars
  BAR_U:  vertical bars bottom-up
  BAR_D:  vertical bars top-down
  BAR_V2: driver supports vertical dual-bars

* edit display.c and create a reference to your LCD table:

     external LCD YourDriver[];

* extend the FAMILY table in display.c with your driver:

     FAMILY Driver[] = {
       { "Skeleton",      Skeleton },
       { "MatrixOrbital", MatrixOrbital },
       { "YourFamily",    YourDriver },
       { "" }
     };

* write the correspondig init(), clear(), put(), bar(), quit() and
  flush()-functions. There's no need to use a framebuffer and display its
  contents with the flush()- call (as in MatrixOrbital.c), you can directly
  write to the display in the put()- and bar()-functions, and use an empty
  flush()-function. But if you have a limited number of user-defined
  characters, and therefore you have to do some sort of 'character reduction'
  or similar stuff, you will have to use a framebuffer and the flush()-call. 
 name='id' value='255b0e18568b1a77ec8644b9cee941b60c378318'/><input type='hidden' name='showmsg' value='1'/><select name='qt'>
<option value='grep'>log msg</option>
<option value='author'>author</option>
<option value='committer'>committer</option>
<option value='range'>range</option>
</select>
<input class='txt' type='search' size='10' name='q' value=''/>
<input type='submit' value='search'/>
</form>
</td></tr></table>
<div class='path'>path: <a href='/dtv-scan-tables.git/log/?id=255b0e18568b1a77ec8644b9cee941b60c378318&amp;showmsg=1&amp;follow=1'>root</a>/<a href='/dtv-scan-tables.git/log/isdb-t?id=255b0e18568b1a77ec8644b9cee941b60c378318&amp;showmsg=1&amp;follow=1'>isdb-t</a>/<a href='/dtv-scan-tables.git/log/isdb-t/br-se-PocoRedondo?id=255b0e18568b1a77ec8644b9cee941b60c378318&amp;showmsg=1&amp;follow=1'>br-se-PocoRedondo</a> (<a href='/dtv-scan-tables.git/log/isdb-t/br-se-PocoRedondo?id=255b0e18568b1a77ec8644b9cee941b60c378318&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-se-PocoRedondo?id=255b0e18568b1a77ec8644b9cee941b60c378318&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-23 13:07:56 -0200'>2016-11-23</span></td><td class='logsubject'><a href='/dtv-scan-tables.git/commit/atsc/us-NTSC-center-frequencies-8VSB?id=0aacef5ed891934344bec98eb24bbc9d83f42019&amp;follow=1'>renaming NTSC file because it doesnt actually use 8VSV, updating channel ↵</a></td><td>Maury Markowitz</td><td>2</td><td><span class='deletions'>-410</span>/<span class='insertions'>+520</span></td></tr>
<tr class='nohover-highlight'><td/><td colspan='5' class='logmsg'>
listings, add channel numbers

This file is renamed to more accurately reflect its contents, as well as including all channels every used in NTSC. This is primarily of historical interest, the ATSC file has a more up-to-date (and much shorter) list to scan against. I notice that my local repo has the rm, but this isn’t reflected in the patch (of course), is there something else I should have done as well?

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;


</td></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>