STRUCT IWL_INIT_EXTENDED_CFG_CMD(9)
π struct iwl_init_extended_cfg_cmd(9) β from the Kernel API Manual, bestie π
okay so picture this: it's a whole manpage, right, and it lives in the Kernel API Manual, and the star of the show is struct iwl_init_extended_cfg_cmd. say hi π
β¨ NAME β¨
struct iwl_init_extended_cfg_cmd β literally its whole job is to mark what commands ucode should wait for before finishing init flows. that's it. that's the vibe. it's the little flag-holder that tells ucode "bestie hold up, wait for these before you call init done" π
πΈ SYNOPSIS πΈ
the way this struct is so simple, honestly iconic:
struct iwl_init_extended_cfg_cmd {
__le32 init_flags;
};
one member. one. __le32. no notes. π
π¦ Members π¦
init_flagsβ the actual flags, and ngl they're values fromiwl_extended_cfg_flagsβ so pop over there if you wanna know what you can actually put in it π
π SEE ALSO π
go read these next, fr fr, they're all in the Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/alive.h:
enum iwl_extended_cfg_flags(9)β the placeinit_flagsgets its values from, iykykstruct iwl_radio_version_notif(9)enum iwl_error_recovery_flags(9)struct iwl_fw_error_recovery_cmd(9)
π real talk: none of these are optional reading if you wanna understand the whole init-flow situation. the manpage said it, not me π«Ά
and that's the whole page, bestie β¨ this lil cutie came from ./drivers/net/wireless/intel/i... (yes it's abbreviated, that's how it shipped, don't come for me π) and it's dated October 2026 β so go forth, wait for your commands, and finish those init flows properly π§ββοΈπ bye!!
π¦ 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