Re: Warning: evdev changes - no auto-grabs anymore

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Fri, Aug 15, 2008 at 05:31:19PM +0300, Daniel Stone wrote:
> On Fri, Aug 15, 2008 at 10:10:10AM -0400, Dmitry Torokhov wrote:
> > On Fri, Aug 15, 2008 at 11:26:29AM +0300, Ville Syrj?l? wrote:
> > > On Fri, Aug 15, 2008 at 11:02:48AM +0300, Daniel Stone wrote:
> > > > On Fri, Aug 15, 2008 at 09:51:59AM +0300, Ville Syrj?l? wrote:
> > > > > I was pondering about the same issue wrt. DirectFB. I wonder if
> > > > > KDSETMODE/KD_GRAPHICS could be extended to take care of this or
> > > > > would it break some existing applications.
> > > > 
> > > > Yeah, I was thinking about that, but that would mean we have issues
> > > > under older kernels. I think the best was what I was proposing, which
> > > > would be EVIOCSERIOUSLYDONTSENDANYCONSOLEINPUTWEWILLDEALWITHIT().
> > > 
> > > Yeah that would be better since support for it could be detected runtime
> > > so the driver could do the right thing when running with a recent kernel,
> > > and it could just fall back to the normal grab with old kernels.
> > 
> > If evdev support in X is maturing why does it even need using tty and
> > mousedev multiplexors? If you just use evdev for all of your devices
> > you would not have the problem of duplicate events coming from 2
> > interfaces.
> 
> We don't, and killing them is fine.  Even so, try doing that, and
> realise that the TTY layer has helpfully spewed out every single thing
> you've typed, oh, and Ctrl-C kills the X server.
> 

[taking xorg list off as it does not take my posts...]

Would not putting VC in raw mode and just ignoring the data coming out
of it take care of this problem?

-- 
Dmitry