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

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

> > I noticed that too, and there was a short discussion recently on the
> > linuxconsole-dev list about that. It seems EV_STATUS messages like
> > EV_CONNECT/EV_DISCONNECT is an idea they liked. I don't know yet if it's
> > better to have these per device or a seperate /dev/input/eventstatus or 
> > both.

Per device. 

> > /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.
 

Q: Why did they deprecate a.out support in linux?
A: Because a nasty coff is bad for your elf.

James Simmons  [jsi...@li...]               ____/| 
fbdev/console/gfx developer                             \ o.O| 
http://www.linux-fbdev.org                               =(_)= 
http://linuxgfx.sourceforge.net                            U
http://linuxconsole.sourceforge.net