å 2010-11-28æç 23:46 +0000ïAlan Coxåéï > Which bit - lots of people own different parts of it, because there is a > lot of it, and people own different sections of currently ongoing > projects. Plus the X DRM folks own the KMS framebuffers, various authors > own their own low level drivers for each card and so on. > > I kind of own the drivers/tty/vt* bits. Don't you see the cosole code ? There is TODO that say , "hey , I need UNICODE support..." I'm not breaking old one to introduce new feature, but fix a little BUG in the TODO list. > I simply don't see how you are going to address the majority of the > worlds languages in kernel space, all the major ones are too complex and > pango is too big and complex to put in kernel as are the needed font > renderers. Most of the needed compositing accelerations are also not > directly exposed in KMS to the console driver as would be needed Simply drawing characters won't need any hw acceleration. It doesn't matter if it is slow. KMS and Wayland will make more people work under console, trust me. > > Your other problem is mode setting, VESA is on its way out, a lot of No, VESA will still be here for another decades. Some fb driver conflict with the X one, even there is a fb driver for you card, you simply won't use it unless it does not conflict with X one. My PC , for example, nvidiafb conflict with X one, so I have to use VESA. > devices today, especially non X86 ones pretty much need X to do any kind > of video management beyond "here is how the firmware console was > configured", and indeed many embedded devices don't have an VT code > enabled at all, just a printk console and possibly ttyprintk, both of > which may well only be talking to the debug ports > > Alan printk console , if redirect to a ttyS? , then the outer Linux world terminal will do UNICODE handling. -- 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
