On Tue, Jun 12, 2007 at 01:35:05AM -0400, Dmitry Torokhov wrote:

On Tuesday 12 June 2007 01:23, Zephaniah E. Hull wrote:

quoted

On Tue, Jun 12, 2007 at 01:19:59AM -0400, Dmitry Torokhov wrote:

quoted

Like I said I would love if xf86-input-evdev did not grab the
device at all.

We have to disable the legacy input handlers somehow, not doing so
simply isn't an option.

I do not follow. If user's xorg.conf does not use /dev/input/mice and
does not use "kbd" driver then grabbing is not required, is it? Now,
as far as I understand, lack of hotplug support in X is the main
obstacle for removing "mouse" and "kbd" drivers, correct?

Sadly, not quite.

The problem is that if the user is not using the mouse and kbd drivers
at all, but is instead using xf86-input-evdev, and no grabbing is done,
then all key presses end up going to the console.

Consider the effects of this when using things like alt-f1 or ctrl-c in
a program in X.

We have to keep the console itself from getting the events in question,
which means either unbinding the kbd interface, or some other sort of
grab, otherwise xf86-input-evdev is completely unusable for keyboards.

Grab support was my initial approach to the problem, in hindsight it
wasn't the right one, but it worked, and it's still needed for the
multi-seat people.

quoted

quoted

But rfkill-input is not a legacy handler. My objection is that with your
solution you still will rob handlers such rfkill-input of events.

Urgh.

So, any thoughts on how to identify legacy input handlers in the input
system?

I guess keyboard and mousedev will have to be flagged as such in kernel.

Ugly, but it works.

-- 
Dmitry

-- 
	  1024D/E65A7801 Zephaniah E. Hull [off-list ref]
	   92ED 94E4 B1E6 3624 226D  5727 4453 008B E65A 7801
	    CCs of replies from mailing lists are requested.

"Microsoft is a cross between the Borg and the Ferengi.  Unfortunately,
they use Borg to do their marketing and Ferengi to do their
programming."
  -- Simon Slavin in asr