Re: evdev planned?

[Michael <macallan%netbsd.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Aug 25, 2012, at 6:44 PM, Thomas Klausner wrote:

> I've forwarded our (nonaka's) changes to xkeyboard-config upstream.
> They are asking:
>
> ----- Forwarded message from bugzilla-daemon%freedesktop.org@localhost -----
>
> https://bugs.freedesktop.org/show_bug.cgi?id=54065
>
> --- Comment #2 from Sergey V. Udaltsov <svu%gnome.org@localhost> 2012-08-25  
> 22:40:15 UTC ---
> Thanks for the materials. If you don't mind, could you please  
> provide a bit of
> context?
> Do you know if NetBSD is planning to introduce evdev driver? I am  
> asking
> because in Linux there is no need in vndr-specific sections, it is  
> all covered
> on the lower levels. I am trying to estimate how important is the  
> code you are
> contributing.
>
> ----- End forwarded message -----
>
> I think that we have no plans for evdev. Is that correct?

There's occasional talk about making all ( or at least the most  
common ) keyboard drivers emit USB-style scancodes when in event mode,  
instead of native ones, which would finally allow the keyboard mux to  
actually combine events from different types of keyboards. No work has  
been done on this ( that I'm aware of at least ), I'll eventually do  
it for Sun and ADB keyboards, someone will have to deal with PS/2 ones  
( the only PS/2 hardware I have is a shark and a few sgimips boxes ).
I'm not exactly familiar with evdev and what else it does besides  
multiplexing input device events. Right now there is no way to tell  
from which device any given event actually came ( when received  
through a mux ), and I'm not sure if there is currently a (useful) way  
to enumerate which devices are hooked up to a given mux. That might  
have to change.
None of this is all that complicated, we're probably fairly close to  
(near) equivalent functionality already, or at least we can get there  
without too much trouble. Adding fields to struct wsevent would break  
binary compatibility though.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEVAwUBUDl5dcpnzkX8Yg2nAQKKrwf+L5QcucswjugxgqH4u4GUmbGCnXpQ/K4B
IGQbNgrNjYxrpR89K7kqmkfjwMflaLs7eWHsQHO/IAPLKPE7bTq3tItInQcbhMro
ouz67bAvREv79IBT9M6FlR/iQcbaz7qSNTB5zGJ0KfFaGYNDvB6/YFTNzHEBBkMT
GAjrZz+XEjhOHwjppzVjB7PfrGgXl4o3YR79F9eKnwP1v4kxhHPsSnucMQNmmgRq
u3ATgyG29KHgiqptjDhPpEnNwVTqTu3NMvFILu6TZZXI4w4PJsotRdsZFvDWL/2X
4Qa6kglZ0BazmAOS8MX8IX0ehi1FYQ3IxklYrZb5s0DFU67uQjlzgA==
=zcKr
-----END PGP SIGNATURE-----