STRUCT IWL_LARI_CONFIG_CHANGE_CMD_V6(9)
π NAME
struct iwl_lari_config_change_cmd_v6 β the whole vibe is "change LARI configuration", a.k.a. the kernel API manual's own little main-character struct β¨ (yes bestie, this is the Kernel API Manual page, we're in the docs now πΈ)
β¨ SYNOPSIS
struct iwl_lari_config_change_cmd_v6 {
__le32 config_bitmap;
__le32 oem_uhb_allow_bitmap;
__le32 oem_11ax_allow_bitmap;
__le32 oem_unii4_allow_bitmap;
__le32 chan_state_active_bitmap;
__le32 force_disable_channels_bitmap;
};
Six __le32 bitmaps, all sitting in a struct together like a little friend group π«Ά and not one of them is optional, okurrr.
π MEMBERS
config_bitmapβ the bitmap of the config commands, and the way this works is each bit triggers a different predefined FW config operation π« so like, one bit = one whole firmware behavior change. Iykyk.oem_uhb_allow_bitmapβ bitmap of UHB enabled MCC sets π short and sweet.oem_11ax_allow_bitmapβ bitmap of 11ax allowed MCCs. And here's the tea: there are two bits per country, one to indicate whether to override, and the other to indicate the value to use π₯ two bits per country, no cap.oem_unii4_allow_bitmapβ bitmap of unii4 allowed MCCs. Same deal, bestie: two bits per country, one to indicate whether to override and the other to indicate allow/disallow unii4 channels πchan_state_active_bitmapβ bitmap for overriding channel state to active β each bit represents a country or region to activate, according to the BIOS definitions. BIOS said what it said.force_disable_channels_bitmapβ bitmap of disabled bands/channels π each bit represents a set of channels in a specific band that should be disabled. Forcing the disable, living its truth.
π¦ SEE ALSO
The kernel file lives at ./drivers/net/wireless/intel/iwlwifi/fw/api/nvm-reg.h β that's the address, screenshot it πΈ β and here's the whole extended friend group, every single one:
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_cmd(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_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)
ngl the versioning on this family is giving "there are many of us and we all have lore" π§ v1, v6, v8 and the un-suffixed one all chilling in the same header, iconic behavior honestly.
Okay that's the whole page bestie, no notes π this was pulled from ./drivers/net/wireless/intel/i... and dated October 2026, and the page itself is struct iwl_l...hange_cmd_v6(9) β go forth and configure your LARI ππ¦β
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms