linux: Parse HID_FIRMWARE_VERSION from uevent for release_number #777
Labels
No labels
3rdparty
Android
API
Author does not respond
bsd
bug
build system/CI
ci-virtual-device
CMake
Contributions Welcome
Core
dependencies
device-specific
documentation
don't_merge
duplicate
enhancement
Example
Haiku
hidraw
hotplug
info required
invalid
libusb
macOS
Misc
Not an issue
question
Release
Test
Test GUI
Windows
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-libusb/hidapi!777
Loading…
Reference in a new issue
No description provided.
Delete branch "FrameworkComputer/hid-firmware-ver"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parse the HID_FIRMWARE_VERSION uevent property to populate release_number for all HID devices. This provides device version information for I2C, Bluetooth, SPI, and virtual HID devices.
For USB devices, the existing bcdDevice lookup from sysfs still takes precedence, maintaining backward compatibility.
The HID_FIRMWARE_VERSION property is being added to the Linux kernel (patch series submitted to linux-input@vger.kernel.org). On kernels without this property, release_number will remain 0 for non-USB devices, preserving existing behavior.
Link: https://lore.kernel.org/linux-input/20260313175659.268094-1-dhs@frame.work/T/#u
Also added here, which looks like it's going into 7.1 by @superm1: https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/commit/?h=for-7.1/lenovo-v2&id=6ca9029c823b7853e980585e757343e0e84227cd
I don't believe I have a way to properly check/test this, but quick googling shows that this is perfectly fine.
Thanks!
if you could add a comment what kernel version this become available (with reference) - that would be great
Yes, we can wait until either Mario or my patch gets merged and I can add a comment
ok, so we wait
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.