linux-console.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: microcai@fedoraproject.org
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, linux-console@vger.kernel.org
Subject: Re: VT console need rewrite
Date: Tue, 7 Dec 2010 12:37:10 -0800	[thread overview]
Message-ID: <20101207123710.4d0e16af@jbarnes-desktop> (raw)
In-Reply-To: <1291025577.9785.7.camel@cai.gentoo>

On Mon, 29 Nov 2010 18:12:57 +0800
Microcai <microcai@fedoraproject.org> wrote:

> 在 2010-11-29一的 11:01 +0100,Andi Kleen写道:
> 
> > To be honest I have doubts its worth it. This was discussed years and
> > years ago and the conclusion back then that people who need unicode
> > fonts should use them in X or another graphical console environment
> > (there are plenty to chose from these days). Has this changed?
> > 
> > -Andi
> > 
> 
> Yes, it change. Linux graphical stuck have changed a lot. With KMS,
> console got a native resolution, and looks very nice.

But really, keep this stuff out of the kernel.  Sure, the kernel can
provide memory and a framebuffer to draw in (subject to the constraints
Jerome already mentioned), but why try to deal with fancy input or font
handling there?  IMO the kernel console should be limited to printing
debug and error information; a separate userspace daemon should handle
input and console support.  It would be great to avoid the need for
CONFIG_VT entirely for the typical Linux system.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2010-12-07 20:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 10:57 VT console need rewrite Microcai
2010-11-28 13:24 ` Theodore Tso
2010-11-28 13:42   ` Microcai
2010-11-28 14:05     ` jonsmirl
2010-11-28 14:29       ` Microcai
2010-11-28 14:49         ` jonsmirl
2010-11-28 19:11         ` Samuel Thibault
2010-11-29  1:10           ` Microcai
2010-11-29  2:49             ` Américo Wang
2010-11-29  2:48               ` Microcai
2010-11-29  8:16             ` Samuel Thibault
2010-11-29  8:20               ` microcai
2010-11-29  8:27                 ` Samuel Thibault
2010-11-29  8:53                   ` Microcai
2010-11-29  8:59                     ` Samuel Thibault
2010-11-28 16:06       ` Lisa Milne
2010-11-28 16:20         ` Microcai
2010-11-28 19:46           ` Ted Ts'o
2010-11-29  1:14             ` Microcai
2010-11-29  8:58               ` Samuel Thibault
2010-11-29  9:32                 ` Microcai
2010-11-29  9:58                   ` Samuel Thibault
2010-11-29 10:11                     ` Microcai
2010-11-29 10:17                       ` Samuel Thibault
2010-11-29 10:40                         ` Microcai
2010-11-29 10:39                           ` Samuel Thibault
2010-12-15 14:45                     ` Pavel Machek
2010-12-15 15:04                       ` Samuel Thibault
2010-11-29  1:55             ` Alexey Gladkov
2010-11-29  2:14               ` Microcai
2010-11-29 14:02                 ` Alan Cox
2010-11-29 17:50                 ` Valdis.Kletnieks
2010-11-29 21:23                   ` Jerome Glisse
2010-11-28 23:46           ` Alan Cox
2010-11-29  1:28             ` Microcai
2010-11-29 14:07               ` Alan Cox
2010-11-30  5:05                 ` microcai
2010-12-20  6:35                   ` Pavel Machek
2010-11-29 10:01 ` Andi Kleen
2010-11-29 10:12   ` Microcai
2010-12-07 20:37     ` Jesse Barnes [this message]
2010-12-13  7:13   ` Pavel Machek
2010-12-13 10:18     ` Alan Cox
2010-12-15 14:40       ` Pavel Machek

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=20101207123710.4d0e16af@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=andi@firstfloor.org \
    --cc=linux-console@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=microcai@fedoraproject.org \
    /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;
as well as URLs for NNTP newsgroup(s).