For full handling of rfkill in GNOME we need the switch state for SW_RFKILL_ALL to be available. It is fine if this information is not available on X11 as we can disable the handling of rfkill in GNOME in that case. See https://bugzilla.gnome.org/show_bug.cgi?id=760517 for some more information on the rfkill issue.
What device does this event come from? Is it a separate kernel device that handles this or is it part of a keyboard? If the former, it's easy to integrate with a few lines of code, the latter would require some extra work.
https://lists.freedesktop.org/archives/wayland-devel/2017-April/033942.html
Note that since this introduces new API/ABI into libinput I'll need at least a rev-by tag from you and ideally an implementation that shows that the approach is actually feasable/good enough. once it's shipped, it cannot be changed.
I'll keep the branch here for easier testing, but I'll still need an ACK for the proposed changes before I make this part of an API set in stone: https://github.com/whot/libinput/tree/wip/rfkill-all
Benjamin, you got an update for me here? I notice the GNOME bug is closed, it's a bit unclear to me if you still want the switch state
Sorry, should have chatted about that at GUADEC. So, the situation is that we effectively don't seem to have any hardware where we actually need this (i.e. it is handled in firmware and/or the driver). That said, reporting it could still improve the user experience by showing an OSD. Other than that, I simply do not feel confident in being able ACK it as I do not currently know enough about Wayland input handling.
Let's close this for now. It's all nice to have theoretical use-cases for it but until we have a request for a specific case it's better to leave things as-is. Otherwise we end up fixing the wrong problem and painting ourselves into a corner.
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.