STRUCT IWL_MCC_UPDATE_RESP_V8(9)
π struct iwl_mcc_update_resp_v8 β Kernel API Manual β¨
okay so bestie, welcome to the struct iwl_mcc_update_resp_v8(9) page π«Ά this is the Kernel API Manual entry, and it's literally the response to MCC_UPDATE_CMD. it carries the new channel control profile map (if it changed) plus the new MCC β that's the mobile country code, iykyk π and plot twist: the new MCC may be different than what you asked for in MCC_UPDATE_CMD, so don't come for me, that's just how it is π
β¨ SYNOPSIS β¨
struct iwl_mcc_update_resp_v8 {
__le32 status;
__le16 mcc;
u8 padding[2];
__le32 cap;
__le16 time;
__le16 geo_info;
u8 source_id;
u8 reserved[3];
__le32 n_channels;
__le32 channels[];
};
no cap, that's the whole vibe of the struct β every field, every type, every bracket π
π Members π
statusβ the status, bestie. peepenum iwl_mcc_update_statusfor the deets πmccβ the new applied MCC. it's giving "this is your country code now" πpaddingβ padding for 2 bytes. yes, literally two bytes of just vibing π¦capβ capabilities for all channels which matches the MCC. every channel that fits, gets its glow-up β¨timeβ time elapsed from the MCC test start, in units of 30 seconds β±οΈ so divide by 30 in your head, not that deepgeo_infoβ geographic specific profile information, seeenum iwl_geo_information. the "where you at" data πΈsource_idβ the MCC source, seeiwl_mcc_source. where the tea came from, fr fr π΅reservedβ for four bytes alignment. alignment queen, keeping things tidy πn_channelsβ number of channels inchannels_data. count 'em π’channelsβ channel control data map, DWORD for each channel. only the first 16bits are used, so the rest of the DWORD is lowkey just there π
π SEE ALSO π
this list is long long, but she ate, so here's every single one, no skips π«Ά
- 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_v3(9)struct iwl_mcc_update_resp_v4(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)
bestie go read them, i'm not kidding, they're all linked for a reason π
and that's the page!! π§ from ./drivers/net/wireless/intel/i... β dated October 2026, filed under struct iwl_...date_resp_v8(9) β mwah, slay, periodt πβ
π¦ 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