On Mon, Nov 29, 2010 at 12:50 PM, <Valdis.Kletnieks@xxxxxx> 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-console" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
