From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mattia Jona-Lasinio <mattia.jona@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Miguel Ojeda Sandonis <miguel.ojeda.sandonis@gmail.com>,
Willy Tarreau <w@1wt.eu>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Walleij <triad@df.lth.se>,
linux-arm-kernel@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
ivan.kuten@promwad.com, lcd-linux-users@lists.sourceforge.net,
Viktar Palstsiuk <viktar.palstsiuk@promwad.com>
Subject: Re: Introducing the LCD-Linux project
Date: Thu, 22 Jul 2010 12:21:11 +0100 [thread overview]
Message-ID: <20100722122111.4cf4ca2f@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <AANLkTikitTGpiE5Oe_P5a4f2OCOnlB9j_LVm5CQhQIno@mail.gmail.com>
On Wed, 21 Jul 2010 14:57:54 +0200
Mattia Jona-Lasinio <mattia.jona@gmail.com> wrote:
> Hi,
>
> this is to introduce the LCD-Linux project (http://lcd-linux.sourceforge.net/),
> a kernel level implementation of a VT102 terminal emulator, optimized for small
> alphanumeric and graphic displays.
The kernel already has a console and that provides an abstract
implementation that is used for everything from text mode displays to vga
to assorted accelerated hardware platforms.
Why do we need a VT102 as well ?
> functions. A solution is therefore to provide a sort of minimal terminal
> emulation in kernel space, that can be accessed through the standard character
> device interface. In this way the problem of the display management is reduced
If you use the existing kernel console interfaces then you don't need to
worry about vt102 v console or having two terminal emulations running.
The basic idea seems sound enough other than that. Another reason for
using the kernel console/vt driver is that you can then also support mini
bitmap displays because a frame buffer driver backed by a driver for a
suitable LCD panel can work nicely because the vt driver can sit on the
fb layer quite happily and fb then implements low level handling for the
pixels.
Alan
next prev parent reply other threads:[~2010-07-22 11:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 12:57 Mattia Jona-Lasinio
2010-07-21 16:38 ` Ben Pfaff
2010-07-22 11:21 ` Alan Cox [this message]
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
2010-07-22 11:00 Mattia Jona-Lasinio
2010-07-22 18:12 ` Ben Pfaff
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=20100722122111.4cf4ca2f@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=ivan.kuten@promwad.com \
--cc=lcd-linux-users@lists.sourceforge.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mattia.jona@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=triad@df.lth.se \
--cc=viktar.palstsiuk@promwad.com \
--cc=w@1wt.eu \
/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®