ENUM BIOS_SOURCE(9)
π enum bios_source(9) β like, the tea on where your BIOS data came from π
okay bestie, pull up a chair, because we're digging into enum bios_source from the Kernel API Manual and honestly? it's giving tiny-but-iconic. it literally just tells you where the BIOS data came from. that's the whole vibe. no cap. β¨
πΈ NAME πΈ
enum bios_source β source of bios data π§
the way that this enum is small but mighty... we love a minimal queen π
π¦ SYNOPSIS π¦
here's the literal shape of it, bestie, copy it exactly:
enum bios_source {
BIOS_SOURCE_NONE ,
BIOS_SOURCE_ACPI ,
BIOS_SOURCE_UEFI
};
look at that. three constants. clean. elegant. ate and left no crumbs π
β CONSTANTS β
okay so these are the three possible moods this enum can be in, and yes they're all important, don't skip:
BIOS_SOURCE_NONEβ BIOS source is not defined π it's the "idk her" option, truly the vibe of a source that hasn't been decided yetBIOS_SOURCE_ACPIβ BIOS source is ACPI π the classic, the original flavorBIOS_SOURCE_UEFIβ BIOS source is UEFI π₯ the modern main character
highkey obsessed with how each one is literally just a one-liner. no drama, no lore, just facts β¨
π SEE ALSO π
alright, buckle up buttercup, because this list is long and we're listing every single one β no skipping, no summarising, that's the rule π«Ά
first up, the file itself lives here:
Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/nvm-reg.h
and then, the whole squad of related pages:
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)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?? forty entries?? she's popular, she has connections, iykyk ππ
ngl bestie, this is a lot of cross-references β if you're chasing all of them down in one sitting, hydrate, stretch, and take breaks. self-care is kernel-doc reading too π
π the cute little sign-off π
that's the whole page, bestie β short, sweet, and absolutely serving π
this one ships out of the kernel source tree at ./drivers/net/wireless/intel/i... and it's dated October 2026 β¨ go forth and know where your BIOS data came from, you absolute icon ππ
π¦ 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