public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Tomas Frydrych <tf+lists.ecos@r-finger.com>
To: ecos-devel@ecos.sourceware.org
Subject: Re: dot matrix display infrastructure
Date: Sun, 15 Jan 2012 18:34:00 -0000	[thread overview]
Message-ID: <4F131C18.20609@r-finger.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1201141940480.3746@vostro>

Hi Sergei,

On 14/01/2012 17:08, Sergei Gavrikov wrote:
>From point of view the eCos BSP concept, it would be great (and quite
> enough) to define needed bitmaps/routines in hal/variant misc sources to
> manage the display as a simple text console, i.e. I mean to setup eCos
> auxiliary diagnostic channel for such a hardware in your HAL and as a
> result to get a chance to run eCos tests using that diagnostic channel.

The diagnostic channel is an interesting idea, but I don't think I want
to build the bitmaps, etc., into the variant hal. The problem of
outputing text on a dot matrix display is generic, not specific to the
board, so should be addressed in a reusable manner.

> I agree with Ilia, but if you plan to develop some kind of an abstract
> library to manage small graphical arrays (of course, first look for any
> portable prototypes with right licence :-) then a right place for such
> packages is eCos 'services' directory.

Ah, I think that is exactly the answer I have been looking for :-)

Tomas

  reply	other threads:[~2012-01-15 18:34 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
2012-01-14 17:09   ` Sergei Gavrikov
2012-01-15 18:34     ` Tomas Frydrych [this message]
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=4F131C18.20609@r-finger.com \
    --to=tf+lists.ecos@r-finger.com \
    --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).