All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: Kernel Summit presentation
Date: Thu, 28 Jul 2005 09:24:17 -0400	[thread overview]
Message-ID: <9e47339105072806242ef1dfbe@mail.gmail.com> (raw)
In-Reply-To: <200507281445.25521.patrakov@ums.usu.ru>

On 7/28/05, Alexander E. Patrakov <patrakov@ums.usu.ru> wrote:
> Jon Smirl wrote:
> 
> > I attached the slides from my kernel summit presentation. The major
> > change is that Linus does not want a new VT state. Instead we should
> > open a new VT, switch it to VT_GRAPHICS, and then refuse to
> > acknowledge VT swap requests. Dave Airlie did another presentation on
> > mode setting and suspend/resume.
> >
> > The simple overview: goal is to get rid of the current VT swap system
> > but replace it with something that looks just like it. To do this the
> > console is split into two halves.
> >
> > 1) kernel console - it is as simple as possible and always guaranteed
> > to work. It is simpler than current fbconsole. It automatically uses
> > whatever mode is set on the monitor. There is only one kernel console
> > - no VTs.
> >
> > 2) user console - implements your normal VTs. Fully accelerated,
> > supports Unicode, etc.
> >
> > No one was really against restructuring the consoles. There was
> > support for a console that always works even when something like X is
> > running.
> 
> I am really interested in this, and want to help (with code, once
> architectural issues are solved). But there is a question:
> 
> How should applications that currently rely upon a kernel VT system being
> present (e.g. Xorg, MPlayer, SDL) be modified? (I mean, is there any proposed
> API for hunting for a free userspace VC?)

If you are really interested the first place to help is getting the
new Xegl Xserver working. It is discussed on the xorg, dri-devel and
dri-egl mailing lists at freedesktop.org.

We probably won't start working on the other console pieces until the
Xserver is ready. Without the Xserver it is hard to do anything in the
new environment.


> 
> --
> Alexander E. Patrakov
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO September
> 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
> 


-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

      parent reply	other threads:[~2005-07-28 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28  8:45 Kernel Summit presentation Alexander E. Patrakov
2005-07-28 13:21 ` Jon Smirl
2005-07-28 13:24 ` Jon Smirl [this message]

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=9e47339105072806242ef1dfbe@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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.