Re: New to the input layer

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

> > Hmm. Let me think about that... What will the application see? I don't see 
> > a type like EV_STATUSCHANGE with events like CONNECT, DISCONNECT, CHANGED?
> 
> Right now, the events from the device will just stop coming in.

What if we create a CONNECT, DISCONNECT event to send to the userland
application ? This way the userland app can decided on what to do.

> Keybdev.c already does that, and keyboard.c (in the complete input
> drivers) is doing it as well.

Ruby doesn't use keybdev.c still right?

> > BTW, are there any known problems with the current backport and console 
> > switching? It seems to lock down some of the modifier keys from time to 
> > time, then you have to press all of them to get them back in a known state.
> > And it seems the LED status sent to USB keyboards is inverted.
> 
> There seems to be a problem with some keys not getting released
> correctly. I wasn't able to find the cause yet.

Console switching is independent of the modifier key handling. I have no
trouble with PC PS/2 keyboards. Sounds like the problem is USB keyboard
specific. What I do see is when I press F1 I get A, F2 I get B etc. I
think this is just a strange keymaping going on. 

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