public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Pfaff <blp@cs.stanford.edu>
To: Mattia Jona-Lasinio <mattia.jona@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: Introducing the LCD-Linux project
Date: Thu, 22 Jul 2010 11:12:02 -0700	[thread overview]
Message-ID: <87aapjbd3h.fsf@benpfaff.org> (raw)
In-Reply-To: <AANLkTil5Gz4i6iGZcaAcU0hg_ynNP1UR7bLwv_VQU6Wm@mail.gmail.com> (Mattia Jona-Lasinio's message of "Thu, 22 Jul 2010 13:00:34 +0200")

Mattia Jona-Lasinio <mattia.jona@gmail.com> writes:
> Ben Pfaff <blp@cs.stanford.edu> writes:
>> When I wanted to solve the same problem for a small
>> serial-connected LCD panel (sold under the name EZIO), I wrote a
>> program called "ezio-term" that has the same functionality but
>> runs entirely in userspace.  It connects to the serial port and
>> speaks the EZIO protocol on the serial port, and it creates a pty
>> and acts like an ANSI terminal on that pty.  Thus, it translates
>> back and forth between the two protocols.
>
> This is indeed a possibility. However, in my opinion, it always suffers
> the same problems: if you change the display, you have to rewrite everything
> from scratch since the protocol for a different display will be different.

It should not be necessary to rewrite everything, only to write
additional code to interface to the particular device.  This code
has to be written in any case, whether it is in userspace or the
kernel.

> I downloaded your program and I'm going through it.

I'm not pushing ezio-term as a general solution, by the way.  It
is clearly very specific to EZIO3 devices.  I'm just pointing out
that its approach is a reasonable alternative.
-- 
Ben Pfaff 
http://benpfaff.org

  reply	other threads:[~2010-07-22 18:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 11:00 Introducing the LCD-Linux project Mattia Jona-Lasinio
2010-07-22 18:12 ` Ben Pfaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-07-21 12:57 Mattia Jona-Lasinio
2010-07-21 16:38 ` Ben Pfaff
2010-07-22 11:21 ` Alan Cox
2010-07-22 11:38   ` Geert Uytterhoeven
2010-07-24 10:31     ` Mattia Jona-Lasinio
2010-07-24 14:43       ` Florian Tobias Schandinat
2010-07-26 20:11         ` Geert Uytterhoeven
2010-07-28 19:24           ` Mattia Jona-Lasinio
2010-07-28 19:39             ` Alan Cox
2010-07-29  9:09               ` Mattia Jona-Lasinio
2010-07-29 16:49               ` James Simmons
2010-07-29 18:05                 ` Alan Cox
2010-07-29 18:39                   ` James Simmons
2010-08-03 12:22                     ` Mattia Jona-Lasinio
2010-08-04 14:29                       ` James Simmons
2010-07-29 15:58             ` James Simmons
2010-07-29 15:17           ` James Simmons
2010-07-26 20:08     ` Geert Uytterhoeven
2010-07-22 19:19 ` Miguel Ojeda
2010-07-24  9:52   ` Mattia Jona-Lasinio

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=87aapjbd3h.fsf@benpfaff.org \
    --to=blp@cs.stanford.edu \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattia.jona@gmail.com \
    /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