[Lcdproc] New glcd driver - your opinion?

[Yura Scheglyuk]

		Hi!

On 10.09.2011 16:00, Markus Dolze wrote:

> yesterday I committed a new driver: glcd. It is supposed to be a 'unified graphic display driver' which makes it more easy to interface LCDd with graphical displays and libraries.
>
> The glcd driver on the other hand does nothing of that. It just renders characters into a framebuffer and instructs the CT-driver to write that image to the display. The CT-driver is responsible to initialize the display and implement double buffering or partial updates as needed.

There are a lot of cheap USB LCDs or USB adapters driven by displaylink 
http://libdlo.freedesktop.org/wiki/ like Lilliput UM-70 or Samsung U70. 
Some of this displays contains Touch Screen. I used workaround to use 
lcdproc on it. Displaylink LCDs can be used as usual framebuffer console 
so I configured lcdproc for "curses" driver. But it's not so good - 
framebuffer console modes is too big for lcdproc tasks, 25 lines or 
more. It would be nice if you'll add support for displaylink LCDs.

> Another option would be to write a small static library (on include it in lcd_lib) that does the font rendering and can be used by other drivers).

Yes, it can provide unified way and minimize code.

-- 
Best regards, Yura.