> Sounds like a good idea. Who is in charge of VT system ? Seems no > one .... 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. 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 Your other problem is mode setting, VESA is on its way out, a lot of 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 -- 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
