public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Kocho <ilijak@siva.com.mk>
To: ecos-devel@ecos.sourceware.org
Subject: Re: dot matrix display infrastructure
Date: Sat, 14 Jan 2012 15:20:00 -0000	[thread overview]
Message-ID: <4F119D17.7010702@siva.com.mk> (raw)
In-Reply-To: <4F0DADB1.1090404@r-finger.com>

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

  reply	other threads:[~2012-01-14 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 15:41 Tomas Frydrych
2012-01-14 15:20 ` Ilija Kocho [this message]
2012-01-14 17:09   ` Sergei Gavrikov
2012-01-15 18:34     ` Tomas Frydrych
2012-01-15 18:26   ` Tomas Frydrych

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F119D17.7010702@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-devel@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).