From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Henk <Henk.Vergonet@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] new 7-segments char translation API
Date: Wed, 1 Jun 2005 10:43:35 +0200 [thread overview]
Message-ID: <20050601084335.GL2417@lug-owl.de> (raw)
In-Reply-To: <20050531220738.GA21775@god.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Wed, 2005-06-01 00:07:38 +0200, Henk <Henk.Vergonet@gmail.com> wrote:
> I know this 7-segments stuff probably won't be used widespread much but it
> could be important to have similar projects use the same notation, and
> use the same concepts.
I don't know if a real API is really needed for that. For example, I
played a bit with the (single) 7-segment display of one of my VAXen
running Linux. Other VAXen only have 8 LEDs in a row. Using these LEDs
for debugging, I most probably just want to output *anything* to the
LEDs so I just use defined constants for that.
However, the principle could be reversed by using a 7-segment "font", a
mapping function and an initializer which specifies which bit belongs to
which bar of the 7-segment display... But maybe it's really worth
mplementing it as a library function...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-01 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 22:07 [RFC] new 7-segments char translation API Henk
2005-06-01 8:43 ` Jan-Benedict Glaw [this message]
2005-06-01 10:04 ` Henk
2005-06-01 12:33 ` Clemens Koller
2005-06-03 20:50 ` Henk
2005-06-04 20:44 ` Henk
2005-06-04 22:53 ` Edgar Toernig
2005-06-06 9:26 ` Henk
2005-06-06 16:19 ` randy_dunlap
2005-06-21 21:30 ` Henk
2005-06-04 15:24 ` Pavel Machek
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=20050601084335.GL2417@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=Henk.Vergonet@gmail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.