On 09.10.2014 17:09, Andriy Gapon wrote:
I looked at the vt code and I was not able to figure out what would be the
proper place there.
Initially I thought that vt_allocate() would be it, but then it seems that
vt_allocate() might not be called. So, perhaps vtterm_cnprobe() ? Something
else?
On 03/10/2014 18:21, Nathan Whitehorn wrote:
On 10/03/14 08:13, Andriy Gapon wrote:
The patch (I am not sure if fbd_attach is the right place to register the
event
handlers):
It's not, I don't think, since fbd_attach() isn't called for all vt backends
(e.g. the VGA and EFI backends
On 30/09/2014 08:47, Andriy Gapon wrote:
I think that currently vt_suspend / vt_resume are called at quite unsuitable
times. For example, vt_suspend performs a vt switch which requires
cooperation
from an X server, but that could be problematic given that some devices may
already be
On 10/03/14 08:13, Andriy Gapon wrote:
On 30/09/2014 08:47, Andriy Gapon wrote:
I think that currently vt_suspend / vt_resume are called at quite unsuitable
times. For example, vt_suspend performs a vt switch which requires cooperation
from an X server, but that could be problematic given
