Re: Linuxconsole-dev digest, Vol 1 #99 - 4 msgs

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

On Sat, Jul 22, 2000 at 08:03:38PM -0400, James Simmons wrote:

> > > /dev/input/eventmixX, based on the EV_STATUS messages and the rules in the
> > > config file. That way most applications do not even need to know that this
> > > can happen and can just keep on reading the FD.
> > > My interest in here, I think it would be nice to attach more than one
> > > device to a eventmixX device, eg. all mice or all keyboards (or both?),
> > > similar to /dev/input/mice. That would make it a lot easier to port
> > > applications to the input layer.
> > 
> > I have never contributed to this list, but I have followed it regularly in 
> > the last 3 months and here's my 2p: applications should not know about
> > all these low level connection stuff, I much prefer the idea of the
> > userland deamon.
> 
> That would be alot more complex than you think. The best thing to so is
> set it up to send a EV_STATUS to the app and it can responded. This way
> the app knows it no longer has the device. KISS.

I agree here. Plus try to connect the device back if the app has it
still open and the device appears again. (temporary disconnect on usb
due to line noise). Send the app EV_STATUS, ST_CONNECT message in that
case.

-- 
Vojtech Pavlik
SuSE Labs