From: Paul LeoNerd Evans <leonerd@leonerd.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
"Antonino A. Daplas" <adaplas@gmail.com>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vt: Do not clear UTF when resetting console
Date: Tue, 3 Apr 2007 22:14:38 +0100 [thread overview]
Message-ID: <20070403221438.77c40a53@nim.leo> (raw)
In-Reply-To: <4611A60F.90505@zytor.com>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On Mon, 02 Apr 2007 17:55:43 -0700
"H. Peter Anvin" <hpa@zytor.com> wrote:
> I think you're missing the whole point of console reset. Its purpose is
> to force the console into a known-good state. The fewer pieces of state
> it leaves unset, the better. To some degree it's less important what
> that state actually is.
Ultimately, does the patch actually change that?
Without this change, utf mode gets reset to zero because that's what the
kernel source code says.
With this change, utf mode gets reset to zero because that's what the
module parameter says and the user hasn't changed it..
.. only with the change, users get the ability to change that policy.
For the last 2 years since I originally submitted that patch, I've been
running it on my box. For those last 2 years, finally, UTF-8 input
actually worked on the VTs. Previous to that, lots of things broke.
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk
ICQ# 4135350 | Registered Linux# 179460
http://www.leonerd.org.uk/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-03 21:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 14:13 Antonino A. Daplas
2007-04-02 17:35 ` H. Peter Anvin
2007-04-03 0:16 ` Antonino A. Daplas
2007-04-03 0:23 ` Jan Engelhardt
2007-04-03 0:53 ` Antonino A. Daplas
2007-04-03 0:55 ` H. Peter Anvin
2007-04-03 21:14 ` Paul LeoNerd Evans [this message]
2007-04-02 19:10 ` Jan Engelhardt
2007-04-03 0:16 ` Antonino A. Daplas
2007-04-03 11:41 ` Martin Mares
2007-04-03 14:51 ` Paul LeoNerd Evans
2007-04-03 15:37 ` Martin Mares
2007-04-04 5:42 ` Antonino A. Daplas
2007-04-04 8:12 ` Jan Engelhardt
2007-04-04 8:26 ` Paul LeoNerd Evans
2007-04-04 16:53 ` Martin Mares
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=20070403221438.77c40a53@nim.leo \
--to=leonerd@leonerd.org.uk \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=hpa@zytor.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome