From: "jonsmirl@gmail.com" <jonsmirl@gmail.com>
To: microcai@fedoraproject.org
Cc: Theodore Tso <tytso@mit.edu>,
linux-kernel@vger.kernel.org, linux-console@vger.kernel.org
Subject: Re: VT console need rewrite
Date: Sun, 28 Nov 2010 09:05:44 -0500 [thread overview]
Message-ID: <AANLkTimQDWHo4-8-H+5bB_uzrgzU=gqbDBuerq983moR@mail.gmail.com> (raw)
In-Reply-To: <1290951770.13526.18.camel@cai.gentoo>
On Sun, Nov 28, 2010 at 8:42 AM, Microcai <microcai@fedoraproject.org> wrote:
> 在 2010-11-28日的 08:24 -0500,Theodore Tso写道:
>> On Nov 28, 2010, at 5:57 AM, Microcai wrote:
>>
>> > Hi, there
>> >
>> > I'm implementing the UNICODE font of the framebuffer console, (see
>> > http://lkml.org/lkml/2010/11/26/50 in case you do not got my email). But
>> > current vt code is too bugy, too many direct assumes about vt buffer,
>> > This makes me so hard to hack. There is TODO telling me to add UNICODE
>> > support, but no room for such code, that's why my patch is so tricky.
>> >
>> > And the code itself, if you'll excuse me, it isn't as beautiful as rest
>> > of the kernel.
>> > So, it really really need a clean rewrite.I'm ganna take is hard job.
>> > And, please tell me if is worth to do so.
>>
>> Yes, the console is code is very old. But please be aware that lots of code (both in the kernel and in userspace) has dependencies upon how the code behaves. So changing it in a way that does not break backwards compatibility is hard. i.e., it is hard to hack for a reason.
>>
>> I would recommend an incremental rewrite (i.e., one patch at a time), as opposed to a rewrite from scratch. Because people will want to be assured that things haven't broken in a horrible way as a result of a complete rewrite...
>>
>> -- Ted
>>
>
> Yeah, I'd also like to rewrite it incrementally. But... who will accept
> that incrementally patch ? It just seems that incremental patch will be
> horrible at the beginning...... It will be discard without a
> reason .....
You can use CONFIG_VT to remove the entire VT subsystem. It might be
easier for you to write an alternative VT system that could be enabled
with a different flag.
The VT system is very old code from the earliest days of Linux.
Thousands of things depend on it both in the kernel and user space. It
will be very hard to make significant changes to it that don't break
lots of dependent code.
Another model to consider... Remove the VT subsystem. Replace it will
a Unicode VT system built in user space. Using the existing kernel
code, leave a single user console in the kernel that would only be
used for system maintenance. Normal users would never see this console
unless their system was really messed up.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Jon Smirl
jonsmirl@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-console" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-28 14:05 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 [this message]
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
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='AANLkTimQDWHo4-8-H+5bB_uzrgzU=gqbDBuerq983moR@mail.gmail.com' \
--to=jonsmirl@gmail.com \
--cc=linux-console@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=microcai@fedoraproject.org \
--cc=tytso@mit.edu \
/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).