History log of /dragonfly/sys/dev/misc/evdev/Makefile (Results 1 – 2 of 2)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc
# 576cd063 08-Dec-2017 Sascha Wildner <saw@online.de>

kernel/evdev: Fix Makefile permission.


# d3d1dd3e 08-Dec-2017 Peeter Must <karu.pruun@gmail.com>

kernel - Bring in evdev from FreeBSD

* This is a port of evdev, the generic input event interface, from
FreeBSD. Wikipedia: "Evdev generalizes raw input events from device
drivers and makes them

kernel - Bring in evdev from FreeBSD

* This is a port of evdev, the generic input event interface, from
FreeBSD. Wikipedia: "Evdev generalizes raw input events from device
drivers and makes them available through character devices in the
/dev/input/ directory."

* It is currently considered experimental since in rare cases it may cause
kernel crash when a device, e.g. usb mouse or keyboard, is detached
while a userland program reading from the corresponding input/eventX
device.

* In order to enable evdev, kernel needs to be rebuilt with 'device evdev'
and 'options EVDEV_SUPPORT'. For debugging, add 'options EVDEV_DEBUG'.

* At present, only ums, kbd and kbdmux can send events to their respective
input/eventX devices. More drivers will be added in due course. The sysctl
kern.evdev.rcpt_mask determines which drivers send events to evdev.

show more ...