dot matrix display infrastructure
Ilija Kocho
ilijak@siva.com.mk
Sat Jan 14 15:20:00 GMT 2012
On 11.01.2012 16:41, Tomas Frydrych wrote:
> Hi,
>
> I am working on a driver for the Freescale Kwikstik LCD, which is a
> segment lcd organized as a dot matrix. As part of that, I have
> prototyped a simple system for drawing text, consisting of a couple of
> minimal bitmapped fonts, a simple font generation tool, and a
> rudimentary API.
>
> I am wondering whether rather than bundling such API into the Kwikstick
> slcd driver package, it would be beneficial to split it out and have a
> common API in io/dmd/ along the lines of:
>
> typedef struct cyg_dmd_device_s cyg_dmd_device;
>
> cyg_dmd_set_pixel (const cyg_dmd_device *display,
> bool on,
> uint x, uint y);
>
>
> typedef struct cyg_font_s cyg_font;
>
> cyg_dmd_draw_string (const cyg_dmd_device *display,
> const cyg_font *font,
> const char *text,
> uint x, uint y);
>
> and perhaps also something like
>
> cyg_dmd_shift_horizontal (const cyg_dmd_device *display,
> bool rotate,
> int pixels);
>
> and then driver implementations in devs/dmd/<some/hw>.
>
> Any thoughts?
Maybe you could first check the Framebuffer. It may be overkill for
small displays but it might be possible to extract functionality that
you need.
> Tomas
More information about the Ecos-devel
mailing list