It would be nice to have evdev support for both mice and keyboard in the kdrive framework. I made a patch that adds that feature to kdrive.
Created attachment 4404 [details] [review] Adds evdev support to kdrive
The default keymapping didn't work for me. I created a patch which contains the default keymapping from Xorg's evdev driver.
Created attachment 5401 [details] [review] changes keymap to default from Xorg evdev driver Should be applied after https://bugs.freedesktop.org/attachment.cgi?id=4404
(In reply to comment #2) > The default keymapping didn't work for me. I created a patch which contains the > default keymapping from Xorg's evdev driver. I'm not able to test it because I use a Brazillian ABNT2 keyboard. I'm trying to figure out the right way to map the keyboard. I don't know if I'm supposed to map the keys in kernel space or within the X server.
I'm changing the product field since kdrive was merged in the xorg tree.
any chance you could rework this so that it applies against the input-hotplug branch of xserver?
I'm willing to do it. Is there any documentation about the changes in this branch?
not really, though you could look at the diff of, say, linux/ps2.c. basically, you need to register a driver. instead of carrying around a type number, you now just get KdPointerInfo * and KdKeyboardInfo *s for every function you provide. so from Init, Enable, Disable, Fini. pass that as your closure into KdRegisterFd, and call KdPostPointerEvent (or whatever it's called) with that, and there's also a z parameter too. i think that's about it. fyi, this has now been merged into master.
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
See http://lists.freedesktop.org/archives/xorg-commit/2007-August/012096.html
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.