ENUM IWL_MVM_VENDOR_CMD(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so this is enum iwl_mvm_vendor_cmd(9) from the Kernel API Manual, and it's literally the supported vendor commands glow-up list. bestie, this enum is the menu of vendor commands. πŸ’…

πŸ¦‹ SYNOPSIS πŸ¦‹

here's the whole enum, no cap β€” code stays exactly as it is:

enum iwl_mvm_vendor_cmd {
    IWL_MVM_VENDOR_CMD_GET_CSME_CONN_INFO ,
    IWL_MVM_VENDOR_CMD_HOST_GET_OWNERSHIP ,
    IWL_MVM_VENDOR_CMD_ROAMING_FORBIDDEN_EVENT

};

πŸ”₯ Constants πŸ”₯

  • IWL_MVM_VENDOR_CMD_GET_CSME_CONN_INFO β€” reports CSME connection info. simple, iconic, done.
  • IWL_MVM_VENDOR_CMD_HOST_GET_OWNERSHIP β€” asks for ownership on the device. This is useful when the CSME firmware owns the device and the kernel wants to use it. In case the CSME firmware has no connection active the kernel will manage on its own to get ownership of the device. When the CSME firmware has an active connection, the user space involvement is required. The kernel will assert the RFKILL signal with the "device not owned" reason so that nobody can touch the device. Then the user space can run the following flow to be able to get connected to the very same AP the CSME firmware is currently connected to:
  • IWL_MVM_VENDOR_CMD_ROAMING_FORBIDDEN_EVENT β€” notifies if roaming is allowed. It contains a IWL_MVM_VENDOR_ATTR_ROAMING_FORBIDDEN and a IWL_MVM_VENDOR_ATTR_VIF_ADDR attributes.

🌈 Description 🌈

okay bestie, here's the actual 13-step flow that the IWL_MVM_VENDOR_CMD_HOST_GET_OWNERSHIP note was hyping up:

  1. The user space (NetworkManager) boots and sees that the device is in RFKILL because the host doesn't own the device. vibe check: not ours yet.
  2. The user space asks the kernel what AP the CSME firmware is connected to (with IWL_MVM_VENDOR_CMD_GET_CSME_CONN_INFO).
  3. The user space checks if it has a profile that matches the reply from the CSME firmware.
  4. The user space installs a network to the wpa_supplicant with a specific BSSID and a specific frequency.
  5. The user space prevents any type of full scan.
  6. The user space asks iwlmei to request ownership on the device (with this command).
  7. iwlmei requests ownership from the CSME firmware.
  8. The CSME firmware grants ownership. slay.
  9. iwlmei tells iwlwifi to lift the RFKILL.
  10. RFKILL OFF is reported to user space.
  11. The host boots the device, loads the firwmare, and connects to a specific BSSID without scanning including IP as fast as it can.
  12. The host reports to the CSME firmware that there is a connection.
  13. The TCP connection is preserved and the host has connectivity. iconic.

πŸ’œ SEE ALSO πŸ’œ

  • Kernel file ./include/uapi/linux/nl80211-vnd-intel.h, plus enum iwl_mvm_vendor_attr(9) β€” go peek for the extra lore, iykyk.

okay that's the whole page, bestie. it came from ./include/uapi/linux, dated October 2026, and it's literally enum iwl_mvm_vendor_cmd(9). mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from