STRUCT IWL_MCC_ALLOWED_AP_TYPE_CMD(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct iwl_mcc_allowed_ap_type_cmd(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so you opened the manpage for struct iwl_mcc_allowed_ap_type_cmd(9) and you're like "what is this even" β€” don't worry, I got you. This is a kernel API page for iwlwifi, and honestly? It's giving regulatory-table realness. Let's go. ✨


🌸 NAME 🌸

struct iwl_mcc_allowed_ap_type_cmd β€” literally just the struct for MCC_ALLOWED_AP_TYPE_CMD. That's it. That's the whole name section. Short queen behavior. πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

Bestie, here's the shape of it, exactly as it is, no cap:

struct iwl_mcc_allowed_ap_type_cmd {
    u8 mcc_to_ap_type_map[UATS_TABLE_ROW_SIZE][UATS_TABLE_COL_SIZE];
    u8 mcc_to_ap_type_unii9_map[UATS_TABLE_ROW_SIZE][UATS_TABLE_COL_SIZE];
};

Two 2D u8 arrays, same dimensions, both vibing with UATS_TABLE_ROW_SIZE rows and UATS_TABLE_COL_SIZE columns. Iconic. 🫢


πŸŽ€ Members πŸŽ€

  • mcc_to_ap_type_map β€” this one is mapping an MCC to 6 GHz AP type support (UATS). like, it's the lookup table where your MCC lives and the 6 GHz AP type support gets decided. main character energy honestly. πŸ’–
  • mcc_to_ap_type_unii9_map β€” and this one's twin: mapping an MCC to UNII-9 AP type support allowed. same table energy, different band, and yes the two of them are literally a matching set. 🧚

πŸ’œ SEE ALSO πŸ’œ

ok this list is LONG and I'm not skipping a single one, so buckle up buttercup β€” every single reference, coming right atcha: 🌈

  • 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_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)

forty-one refs, zero skipped, we ate that. πŸ”₯


ngl bestie, if you're poking at MCC tables and UATS maps you're deep in iwlwifi regulatory land β€” read the SEE ALSO list, it's literally the whole neighborhood. πŸ’€

and that's the tea! πŸ“ sign-off time: this page lives over in ./drivers/net/wireless/intel/i…, it's dated October 2026, and the whole thing answers to the name struct iwl_m…_ap_type_cmd(9). periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from