Opened 4 years ago
Closed 4 years ago
#14175 closed enhancement (fixed)
libevdev-1.10.0 (Xorg Driver)
Reported by: | Bruce Dubbs | Owned by: | blfs-book |
---|---|---|---|
Priority: | normal | Milestone: | 10.1 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
New minor version.
Note:
See TracTickets
for help on using tickets.
The first rc for libevdev 1.10 is now available.
Most notably: a bunch of FreeBSD fixes that makes the uinput-related code-paths working. Other than that, just a few tidyups.
Kernel 5.8 changed the SW_MAX define from 0x0f to 0x10. In some niche cases this causes issues if libevdev and the software build against different headers and thus end up with different values. So far I've only had this happen in tests that specifically trigger those edge cases, so consider this a general heads-up only, you shouldn't need to worry about. Especially if you have been using libevdev_event_type_get_max() instead of hardcoding SW_MAX.
===========
The second rc for libevdev 1.10 is now available.
One new API, libevdev_disable_property(), which is the opposite of libevdev_enable_property(). Expect the 1.10 release to come within the next few days.
===========
libevdev 1.10 is now avalilable. As already noted in the previous rcs, the main changes are (copied from the annouce emails):
One new API, libevdev_disable_property(), which is the opposite of libevdev_enable_property().
A bunch of FreeBSD fixes that makes the uinput-related code-paths working.
Kernel 5.8 changed the SW_MAX define from 0x0f to 0x10. In some niche cases this causes issues if libevdev and the software build against different headers and thus end up with different values. So far I've only had this happen in tests that specifically trigger those edge cases, so consider this a general heads-up only, you shouldn't need to worry about. Especially if you have been using libevdev_event_type_get_max() instead of hardcoding SW_MAX.