mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henk <Henk.Vergonet@gmail.com>
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] new 7-segments char translation API
Date: Fri, 3 Jun 2005 22:50:14 +0200	[thread overview]
Message-ID: <20050603205014.GB3360@god.dyndns.org> (raw)
In-Reply-To: <429DAB07.1050900@anagramm.de>

On Wed, Jun 01, 2005 at 02:33:11PM +0200, Clemens Koller wrote:
> Hello, Henk!
> 
> >1 - Notation
> >
> >Make things potential interoperable, your character sets will be
> >portable to other LCD devices.
> >
> >   +-a-+
> >   f   b
> >   +-g-+   => encodes to =>  MSb  76543210 LSb
> >   e   c                           gfedcba
> >   +-d-+                     bit7 is reserved.
>           (x)
> 
> Bit7 is propably useful for the decimal point (x)?
> Well, that's how I used it some time ago.
>
Hi Clemens,

I think it could. However for conveniance I implemented it as a
seperate addressable entity.

For userspace I want things to be simple, just a simple echo should be
sufficient to manipulate the LCD:

For example:

   echo -n "3 A  1.0 0 0" > /sys/.../line1

in order to set the lcd. In order to read back the contents of the lcd:

  cat  /sys/.../line1
  8.8.8.8.8.8.8.8.888  <= format string, see below
  3 A   1.0 0 0        <= contents


When the dot is encoded in the digit you would lose a digit when a 
dot is printed. In a two segment display with dots "1.0" can not be 
printed.

I don't want kernelcode trying to decide if it should collapse "1." in
a single digit or not. These implicit functional rules are always a
pain in the ass when not implmented at the right level. And don't 
belong in the kernel.

Best regards,
Henk


/* Format string description:
 *
 * From a user space perspective the world is seperated in "digits" and "icons".
 * A digit can have a character set, an icon can either be ON or OFF.
 *
 * Format specifier
 *   '8' :  Generic 7 segment digits with individual addressable segments
 *
 *   Reduced capabillity 7 segm digits, when segments are hard wired together.
 *   '1' : 2 segments digit only able to produce 1.
 *   'e' : Most significant day of the month digit,
 *         able to produce at least 1 2 3.
 *   'M' : Most significant minute digit,
 *         able to produce at least 0 1 2 3 4 5.
 *
 *   Icons or pictograms:
 *   '.'  : For example like AM, PM, SU, a 'dot' .. or other single segment
 *          elements.
 */


  reply	other threads:[~2005-06-03 20:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 22:07 Henk
2005-06-01  8:43 ` Jan-Benedict Glaw
2005-06-01 10:04 ` Henk
2005-06-01 12:33 ` Clemens Koller
2005-06-03 20:50   ` Henk [this message]
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=20050603205014.GB3360@god.dyndns.org \
    --to=henk.vergonet@gmail.com \
    --cc=clemens.koller@anagramm.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®