Re: X compiled for evdev?

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

On Tue, Jul 23, 2002 at 08:29:24PM +1000, Brad Hards wrote:

> On Tue, 23 Jul 2002 17:13, 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.
> I like this. However it appears to only support a single device. Any reason?

It should not. For every open() of that node in /dev, you get a new input
device created.

-- 
Vojtech Pavlik
SuSE Labs