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.

For a lot of applications I think this will be true.

quoted

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.

There are quite a few, but ttyprintk means that if you've got a printk
console you've got a console "tty" at least for output. End of problem
therefore.

Thanks for the answers. So I can concentrate on the user-space parts
and maybe later implement some drmcon'ish driver.

I think so. And bear in mind a "drmcon'ish driver" for rescue could be a
shared library you can link the boot environment with, one that makes
minimal use of drm and /dev/input to implement a very basic vt.

Alan