|WikiProject Linux||(Rated Stub-class)|
I replaced the stub sentence. The article before read it is about only usb devices, no, I have a few usb devs that have /dev/input/event* files but also hardware like common keyboards have their own file there.
kernel docs read: evdev is the generic input event interface. It passes the events generated in the kernel straight to the program, with timestamps. The API is still evolving, but should be useable now. It's described in section 5.
I've partially rewritten the article, aiming to make it easier for non-techies to understand. Comments and improvements welcome.
Sourcing the article is difficult. It turns out there is not much user-level documentation for evdev, and developers seem to be expected to simply read the code (which is quite straightforward, BTW).
Here are three sources I didn't use:
- Hards, Brad (Feb 2003). "The Linux USB Input Subsystem, Part I". Linux Journal.
Describes how the evdev architecture works for USB input devices. Does not use the word 'evdev'.
- Hards, Brad (Mar 2003). "Using the Input Subsystem, Part II". Linux Journal.
Describes how userland code uses evdev, again without using the word 'evdev'.
- "XStrikeForce/InputHotplugGuide". Debian Wiki.
A brief but good description X.org, evdev and hotplugging followed by a configuration HOWTO. The rules for sourcing articles generally exclude wiki pages, but this might be an exception.
Cheers − CWC 10:45, 15 November 2010 (UTC)
Concerning the recent image additions
I've reverted the recent addition of images on this article because, like in other articles, the images are only marginally relevant and are being inserted into articles where they do not belong. Some image that vaguely shows, buried within irrelevant diagrams, that libEvdev is used by "Video game" via "SDL Input" with a box below it that contains the word "evdev" does not enhance a reader's understanding of the subject in any meaningful way. SDL Input isn't elaborated upon, nor what part evdev plays in any of that. That's why I have reverted these images, because while there may be an article where these are relevant, this article isn't it. - Aoidh (talk) 21:00, 18 July 2014 (UTC)
Problems of this article
This article is a complete mess. Official website link directs to one thing, while the text describes another two different things. Initially this article was about Linux input driver. So I am rewriting it. --22801759th (talk) 20:40, 15 October 2014 (UTC)
- I think it makes perfect sense to discuss both the kernel interface and the X.org driver in this same article. After all, X.org is the primary user of this interface. Just make it sufficiently clear that they are distinct things.
- What the article was "initially" is not very relevant. -- intgr [talk] 22:19, 15 October 2014 (UTC)
- Frankly, I don't think this topic deserves an article. It has issues with Notability as a separate piece of software, and it is not widely described in main article to have a separate article. The same applies for libevdev and xf86-input-evdev.
- Various pages on the internet refer to xf86-input-evdev as evdev. That's probably because xf86-input-evdev was initially called evdev. Relatively new README file of xf86-input-evdev repository describes it as xf86-input-evdev and release branch names change from evdev to xf86-input-evdev, while man page started in 2006 says it's evdev.
- It definitely makes sense to mention that X.org uses evdev, but we cannot fill the article with X.org specific details, not connected to Linux kernel. If that details are notable then they have to to be mentioned in X.org or have separate article. --22801759th (talk) 00:08, 16 October 2014 (UTC)
Not only Linux
FreeBSD and possibly others have adopted this as well now Commit. This article should be generified to be less Linux specific. — Preceding unsigned comment added by Mnd999 (talk • contribs) 09:20, 19 September 2016 (UTC)