Re: X compiled for evdev?

[Vojtech P. <vo...@su...>]

On Tue, Jul 23, 2002 at 11:46:45AM +0200, Franz Sirl wrote:
> At 09:13 23.07.2002, Vojtech Pavlik wrote:
> >On Sun, Jul 21, 2002 at 12:22:11PM -0700, James Gibson wrote:
> > > On Sun, 21 Jul 2002, Scot Wilcoxon wrote:
> > > > A long time ago, James Simmons generously inscribed:
> > > >  >> You can have multiple keyboards:
> > > >  >  o either they get merged and look like one keyboard
> > > >  >  o or, if you use the X Input extension, it appears as another
> > > >  > input device.
> > > >
> > > > I just wanted to point out a need for input "filters".  It would be
> > > > helpful to be able to redirect input from specific devices, or to filter
> > > > input through a userland program.
> > > <snip>
> >
> >We have the uinput device, which allows the userspace to create a new
> >input device and feed it with synthetic events. I guess this is enough.
> 
> Great, that's at least enough to finally replace the mouse button emulation 
> in drivers/macintosh/mac_hid.c with a userspace daemon, probably as an 
> addition to the already existing pbbuttonsd.
> 
> What I'm still unsure about is the best way for a daemon to detect newly 
> added evdev devices. Or is continously scanning /dev/input/ the best way? 
> What did happen to the idea of a status device for connect/disconnect/etc 
> messages?

There is /proc/bus/input/devices you can read and select() on. The input
core also knows how to call /sbin/hotplug with proper arguments and
environment. The first will probably go away over time in favor of the
second.

-- 
Vojtech Pavlik
SuSE Labs