STRUCT IWL_TAS_CONFIG_CMD_V4(9)
π struct iwl_tas_config_cmd_v4(9) β a vibe check from the Kernel API Manual β¨
okay bestie, so this one is from the Kernel API Manual, and it's literally the struct iwl_tas_config_cmd_v4 page. yes it's a C struct. yes it's niche. but it's our niche struct and we're gonna understand it together π«Ά
πΈ NAME πΈ
struct iwl_tas_config_cmd_v4 β configures the TAS. that's it, that's the whole gig. it configures the TAS. iconic of it honestly π
β¨ SYNOPSIS β¨
here's the struct in all its glory, no cap, character for character:
struct iwl_tas_config_cmd_v4 {
u8 override_tas_iec;
u8 enable_tas_iec;
u8 usa_tas_uhb_allowed;
u8 uhb_allowed_flags;
};
look at those four little u8 fields. four. little. guys. main character energy, each and every one π
π¦ Members π¦
okay so let's meet the cast, one by one:
override_tas_iecβ this one indicates whether to override the default value of the IEC regulatory. like, are we doing our own thing here or nah? it's giving "i'll take it from here" πenable_tas_iecβ and in caseoverride_tas_iecis set, this tells you whether the IEC regulatory is enabled or disabled. it's a package deal, bestie β this field only really matters when its sibling is doing its thing πusa_tas_uhb_allowedβ if set, allow TAS UHB in the USA πΊπΈβ¨ short, sweet, and to the point. we love a straightforward flag.uhb_allowed_flagsβ for the details on this one, go check outenum iwl_tas_uhb_allowed_flags(it's linked below, iykyk). it's the "see also" of the group chat π
π SEE ALSO π
literally the whole extended friend group, all here, all linked, all important. no skips, no shortcuts, we're listing everyone fr fr:
Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/nvm-reg.hβ yes, that's where this lives, go say hi π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)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. the whole group chat. hydrate before you click through all of those π
ngl, this page is 100% reference material β no defaults to guess at, no exit statuses, no signals, no warnings. just a struct and its people. read it, cite it, move on. periodt. π
β and that's the page!! this little beauty ships from ./drivers/net/wireless/intel/i... and is dated October 2026 β same title, struct iwl_t...onfig_cmd_v4(9), top and bottom, keeping it consistent bestie ππ bye, love u, go configure that TAS! πΈπ¦
π¦ 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