STRUCT IWL_MCC_UPDATE_RESP_V3(9)
π¦ NAME π¦
ok so bestie, welcome to struct iwl_mcc_update_resp_v3 β yes that's the whole name, it's a whole mouthful, i know π β from the Kernel API Manual. this is literally the response to MCC_UPDATE_CMD, and it's carrying the new channel control profile map (if it changed, which, vibes) plus the new MCC (that's mobile country code for the uninitiated π«Ά). and plot twist: the new MCC might not even be the one you asked for in MCC_UPDATE_CMD. it's giving "i heard you but i did my own thing" energy, no cap.
β¨ SYNOPSIS β¨
ok here's the whole shape of her, exactly as she is, don't touch:
struct iwl_mcc_update_resp_v3 {
__le32 status;
__le16 mcc;
u8 cap;
u8 source_id;
__le16 time;
__le16 geo_info;
__le32 n_channels;
__le32 channels[];
};
π Members π
statusβ the status field, lowkey the main character of "did this work or not". seeenum iwl_mcc_update_status.mccβ the new applied MCC. the fresh one. the upgrade. πcapβ the capabilities for all channels which matches the MCC.source_idβ where the MCC came from, seeiwl_mcc_source.timeβ time elapsed from the MCC test start, and yes it's in units of 30 seconds, so do the math before you @ me πgeo_infoβ geographic specific profile information, seeenum iwl_geo_information.n_channelsβ number of channels inchannels_data.channelsβ the channel control data map, DWORD for each channel. and here's the catch bestie: only the first 16bits are used. only. the first. 16. bits. the rest is just... there. decorative. π
π SEE ALSO π
ok prepare yourself, this list is long and she ate, fr fr. everything lives in the 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_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_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 i said. she ate and left no crumbs π
ngl bestie, the time unit thing (30 seconds!!) and the "only first 16bits" thing are the two spots where people get humbled. read them twice. i'm not being dramatic, i'm being accurate. π
πΈ ok that's the whole page, mwah π β this lil gem lives over in ./drivers/net/wireless/intel/i..., dated October 2026, and it's part of the Kernel API Manual as struct iwl_...date_resp_v3(9). go forth and configure your channels, you gorgeous nerd π§ββοΈβ¨
π¦ 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