Date: Wed, 13 Sep 2006 15:06:39 +0100
From: Ben Dooks <ben-linux@fluff.org>
To: Miguel Ojeda Sandonis <maxextreme@gmail.com>
Cc: greg@kroah.com, alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] LCD Display Driver lcddisplay, ks0108, cfag12864b
Message-ID: <20060913140639.GA26265@home.fluff.org>
References: <20060912193212.1407209b.maxextreme@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060912193212.1407209b.maxextreme@gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 920
Lines: 26

I think there would be a case for splitting the lcd
drivers into two layers, one to deal with the hardware
talking to an lcd device (such as an parallel port)
and the second to deal with the command sequences
being sent.

For instance, we have two boards based on ARM which
use a CPLD to decode CS1 and CS2, etc. This would
mean re-writing your driver (and anyone elses)
depending on what sort of LCD we would like to
connect to these.

If there was an generic device driver, then you
could export the writing of bytes to user-space
and have them use the hardware to do any protocol
they liked.

-- 
Ben (ben@fluff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/