All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Cc: Dave Airlie <airlied@linux.ie>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Kernel Summit presentation
Date: Wed, 27 Jul 2005 11:30:08 -0400	[thread overview]
Message-ID: <9e47339105072708302ee6cf22@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

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 CC'd Dave/Ben. They may have a summary of their talk.

-- 
Jon Smirl
jonsmirl@gmail.com

[-- Attachment #2: ks.sxi --]
[-- Type: application/vnd.sun.xml.impress, Size: 46659 bytes --]

             reply	other threads:[~2005-07-27 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27 15:30 Jon Smirl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-28  8:45 Kernel Summit presentation Alexander E. Patrakov

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=9e47339105072708302ee6cf22@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=airlied@linux.ie \
    --cc=benh@kernel.crashing.org \
    --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.