STRUCT IWL_NVM_ACCESS_CMD(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct iwl_nvm_access_cmd(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this is the page for struct iwl_nvm_access_cmd, and honestly? it's giving "tiny struct, big job" energy. πŸŽ€


✨ NAME ✨

struct iwl_nvm_access_cmd β€” literally the request you send so the device hands over an NVM section. that's the whole vibe. 🫢


🌸 SYNOPSIS 🌸

struct iwl_nvm_access_cmd {
    u8 op_code;
    u8 target;
    __le16 type;
    __le16 offset;
    __le16 length;
    u8 data[];
 };

no cap, that's the whole shape of it. ✨


πŸ¦‹ Members πŸ¦‹

  • op_code β€” the operation, and it's an enum iwl_nvm_access_op. so like, what are we even doing here.
  • target β€” which target we're talking to, typed as enum iwl_nvm_access_target.
  • type β€” the section type, enum iwl_nvm_section_type. basically which NVM section we're obsessed with rn.
  • offset β€” offset in bytes into the section. yes bestie, bytes. count them carefully. πŸ’€
  • length β€” in bytes, to read/write. so how much of the section we're grabbing (or yeeting in).
  • data β€” if write operation, the data to write. On read its empty. that's it, that's the flex. πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

lowkey the best part, because this struct has so many friends. main character energy by association fr fr. 🌈

  • Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/nvm-reg.h
  • enum iwl_regulatory_and_nvm_subcmd_ids(9)
  • enum iwl_nvm_access_op(9)
  • enum iwl_nvm_access_target(9)
  • enum iwl_nvm_section_type(9)
  • struct iwl_nvm_access_resp(9)
  • enum iwl_nvm_info_general_flags(9)
  • struct iwl_nvm_get_info_general(9)
  • enum iwl_nvm_mac_sku_flags(9)
  • struct iwl_nvm_get_info_sku(9)
  • struct iwl_nvm_get_info_phy(9)
  • struct iwl_nvm_get_info_regulatory_v1(9)
  • struct iwl_nvm_get_info_regulatory_v2(9)
  • struct iwl_nvm_get_info_rsp_v3(9)
  • struct iwl_nvm_get_info_rsp_v4(9)
  • struct iwl_nvm_get_info_regulatory(9)
  • struct iwl_nvm_get_info_rsp(9)
  • struct iwl_nvm_access_complete_cmd(9)
  • struct iwl_mcc_update_cmd(9)
  • enum iwl_geo_information(9)
  • struct iwl_mcc_update_resp_v3(9)
  • struct iwl_mcc_update_resp_v4(9)
  • struct iwl_mcc_update_resp_v8(9)
  • struct iwl_mcc_chub_notif(9)
  • struct iwl_tas_config_cmd_common(9)
  • struct iwl_tas_config_cmd_v3(9)
  • enum iwl_tas_uhb_allowed_flags(9)
  • struct iwl_tas_config_cmd_v4(9)
  • enum bios_source(9)
  • struct iwl_bios_config_hdr(9)
  • struct iwl_lari_config_extension_cmd(9)
  • struct bios_value_u32(9)
  • struct iwl_tas_config_cmd(9)
  • enum iwl_lari_config_masks(9)
  • struct iwl_lari_config_change_cmd_v1(9)
  • struct iwl_lari_config_change_cmd_v6(9)
  • struct iwl_lari_config_change_cmd_v8(9)
  • struct iwl_lari_config_change_cmd(9)
  • struct iwl_pnvm_init_complete_ntfy(9)
  • struct iwl_mcc_allowed_ap_type_cmd_v1(9)
  • struct iwl_mcc_allowed_ap_type_cmd(9)

like… a whole friend group. iykyk. πŸ’œ


ngl bestie, this is kernel API territory β€” read the header, check the enums, don't go guessing at field behaviour. the struct tells you the fields, not the whole story. 🧚

mwah, that's the page πŸ’…βœ¨ this cutie came out of ./drivers/net/wireless/intel/i..., dated October 2026, and it's filed under struct iwl_nvm_access_cmd(9). slay, go read the header bestie πŸ“πŸ¦‹

πŸ“¦ where this page comes from