[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTim5RHNQnFG-fUJ=zXk1Zz4uhf3+dLGU4MwXq5Sr@mail.gmail.com>
Date: Mon, 29 Nov 2010 16:23:24 -0500
From: Jerome Glisse <j.glisse@...il.com>
To: Valdis.Kletnieks@...edu
Cc: microcai@...oraproject.org,
Alexey Gladkov <gladkov.alexey@...il.com>,
"Ted Ts'o" <tytso@....edu>, Lisa Milne <lisa@...net.com>,
"jonsmirl@...il.com" <jonsmirl@...il.com>,
linux-kernel@...r.kernel.org, linux-console@...r.kernel.org,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: VT console need rewrite
On Mon, Nov 29, 2010 at 12:50 PM, <Valdis.Kletnieks@...edu> wrote:
> On Mon, 29 Nov 2010 10:14:06 +0800, Microcai said:
>
>> The thing is, you really should agree that, implementing UNICODE font in
>> kernel isn't a bad idea.
>
> Let us know when you have implemented support for bidirectional
> scripts that require compositing or half-spacing characters. Without
> blowing out the 8K kernel stack.
>
> Doing it *right* is important:
>
> http://gizmodo.com/382026/a-cellphones-missing-dot-kills-two-people-puts-three-more-in-jail
>
> Two dead, three in jail. All because of broken font support. That's a good
> reason to not even try unless you can do it *right*.
>
>
Side point, KMS people would like to see the direct memory access to
fb buffer vanish, right now we are wasting vram to keep a front buffer
around for fb. So somethings like always using some callback to access
(write/read) to fb buffer.
Cheers,
Jerome Glisse
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists