From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Ran Benita <ran234@gmail.com>, dri-devel@lists.freedesktop.org
Subject: Re: [ANNOUNCE] kmscon: Lazy-web's DRM based terminal emulator
Date: Wed, 28 Mar 2012 21:14:20 +0300 [thread overview]
Message-ID: <20120328181420.GL4917@intel.com> (raw)
In-Reply-To: <20120328103020.238eab42@jbarnes-desktop>
On Wed, Mar 28, 2012 at 10:30:20AM -0700, Jesse Barnes wrote:
> On Tue, 27 Mar 2012 16:57:29 +0200
> David Herrmann <dh.herrmann@googlemail.com> wrote:
>
> > Hi
> >
> > Motivated by Jesse's letter to the lazyweb [1] I worked on a kmscon
> > program. It provides a
> > terminal-emulator similar to the in-kernel terminal-emulator based on
> > DRM. It is written
> > from scratch and needs as external dependencies only mesa (libdrm,
> > libgbm, libEGL, libGLESv2),
> > udev, xproto (build-time dep), libxkbcommon, freetype2 and currently
> > glib (only for unicode support).
> > It uses a very recent version of libxkbcommon but it should be easy to
> > fix ./src/kbd_xkb.c if
> > you use an older version (or use --disable-xkbcommon to use a very
> > basic keyboard handler).
>
> Awesome! Now get the distros to pick this up and turn off CONFIG_VT! :)
>
> Ville's comment about a texture atlas is a good one, if nothing else I
> think it should improve cache behavior.
You could also render a large batch of glyphs with just a single
glDrawElements()/glDrawArrays() call. Looks like the current code
does a glDrawArrays() for each glyph.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2012-03-28 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 14:57 [ANNOUNCE] kmscon: Lazy-web's DRM based terminal emulator David Herrmann
2012-03-27 15:59 ` Ville Syrjälä
2012-03-28 9:38 ` David Herrmann
2012-03-28 17:30 ` Jesse Barnes
2012-03-28 18:14 ` Ville Syrjälä [this message]
2012-04-01 16:45 ` David Herrmann
2012-04-01 16:49 ` David Herrmann
2012-04-01 21:40 ` Alan Cox
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=20120328181420.GL4917@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=ran234@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