From 4477d33dd8b4bdba8f8af688fc050bb25d71183f Mon Sep 17 00:00:00 2001
From: reinelt <>
Date: Sat, 5 Nov 2005 06:34:09 +0000
Subject: [lcd4linux @ 2005-11-05 06:34:09 by reinelt] README.Drivers removed

---
 README.Drivers | 58 ----------------------------------------------------------
 1 file changed, 58 deletions(-)
 delete mode 100644 README.Drivers

diff --git a/README.Drivers b/README.Drivers
deleted file mode 100644
index 98628ec..0000000
--- a/README.Drivers
+++ /dev/null
@@ -1,58 +0,0 @@
-#
-# $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. 
-- 
cgit v1.2.3