Hi Alan On Wed, May 16, 2012 at 6:14 PM, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote: >> That's just some of my ideas on this topic. Maybe you can give me some >> hints whether it actually makes sense ;) > > For a lot of hardware it may not matter. If it goes bang you boot with a > debugging kernel (one containing a vt driver) > > If your user space goes castors up early then you are going to need input > facilities anyway (consider the fedora rescue mode in dracut for example) So you are basically saying that such an drmcon driver isn't needed, anyway? If we keep backwards compatibility to CONFIG_VT, everyone who wants a boot-log on the display just needs to enable CONFIG_VT. Sounds reasonable. > As far as compatibility goes we have the ttyprintk driver which just > provides a fake tty which types nothing and whose output goes to the > console. I haven't found any applications that fail without /dev/tty, however, thanks for the hint. > Alan Thanks for the answers. So I can concentrate on the user-space parts and maybe later implement some drmcon'ish driver. Regards David -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
