STRUCT RFKILL_EVENT_EXT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so this is the <pink>Kernel API Manual</pink> page for struct rfkill_event_ext β€” the struct that handles events for userspace on /dev/rfkill πŸ’–


πŸŽ€ SYNOPSIS πŸŽ€

struct rfkill_event_ext {
    __u32 idx;
    __u8 type;
    __u8 op;
    __u8 soft;
    __u8 hard;
    __u8 hard_block_reasons;
 };

that's the whole shape of it, bestie 🫢


πŸ’… MEMBERS πŸ’…

  • idx β€” the index of the dev rfkill. like, which one it is ✨
  • type β€” the type of the rfkill struct 🌸
  • op β€” the operation code πŸ’«
  • soft β€” the soft state, and it's 0/1 only, no in-between πŸŽ€
  • hard β€” the hard state, also strictly 0/1 ⭐
  • hard_block_reasons β€” this one only counts (valid) if hard is set, iykyk. it's one or several reasons, pulled from enum rfkill_hard_block_reasons πŸ”₯

🌈 DESCRIPTION 🌈

so this structure? it's the one used for userspace communication on /dev/rfkill πŸ’– and it works both directions β€” it carries events from the kernel, and it carries control to the kernel. main character energy, honestly πŸ‘‘

also: see the extensibility docs below πŸ‘‡ (yes, for real, they're in the SEE ALSO, go look)


πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./include/uapi/linux/rfkill.h
  • enum rfkill_type(9)
  • enum rfkill_operation(9)
  • enum rfkill_hard_block_reasons(9)
  • struct rfkill_event(9)
  • Extensibility(9)

okay that's the whole page, no cap 🧚 this came to you straight from ./include/uapi/linux, dated October 2026 β€” and it's literally titled struct rfkill_event_ext(9), in case you forgot already 😭 go touch /dev/rfkill responsibly, love u, bye πŸ’œ

πŸ“¦ where this page comes from