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 ([email protected], 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
