Re: mousedev patch

[James S. <jsi...@tr...>]

> > This will be less acute when a single interface is available which
> > provides applications with all available information (such as James's
> > suggestion of an evdev mixer which adds a field giving the minor
> > number of the evdev device correspending with the source).
> 
> Do we really need an evdev mixer? Isn't it easier to just try to open
> and read all the evdev devices?

Actually the problem is hot plug. For the software at work I basically
have a thread that runs so often to see if a new device is attached.
This method really sucks. We really need away to know when a new device
has attached. I remember you mentioned having something in proc for that. 
Perhaps we should explore this path?