Re: New to the input layer

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

> 3) As you suggest, EV_STATUS or something like that telling the app the
> device is gone and/or reconnected.

I like this approach but instead of expensive ioctl calls we send
EV_STATUS events.

> > Heh, but they mix to "legacy" console devices (or do I miss something 
> > here?), I want an event protocol device :-). Remember, on PPC we used ADB 
> > scancodes so far. I don't wan't to change to AT scancodes now and then 
> > again to events, when the input layer is 100% ready. That's why I want a 
> > /dev/input/keyboards, running the event protocol. I'll make it CONFIG_PPC 
> > specific if you want.

Legacy devices. The way ruby works for keyboards is:

"native keyboard" -> event -> input -> /dev/event
 PS/2 or ADB etc	   |
			   |
			   ------- keyboard.c -> console system.

So a /dev/input/event should be created and the ADB input driver
translates it to a event packet. The console system works with these event
packets. This allows for a universal interface for the console with
keyboards. At the same time it allows for /dev/input/eventX to be used for
any type of keyboard. 
		 	
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