mpt3sas_config_get_bios_pg2(9)
π mpt3sas_config_get_bios_pg2(9) π
okay bestie, welcome to the Kernel API Manual ~ yes it's giving very "I read kernel source for fun" but honestly? iconic. this page is all about mpt3sas_config_get_bios_pg2 and it's gonna be so easy, i promise π«Ά
β¨ NAME β¨
mpt3sas_config_get_bios_pg2 β obtain bios page 2
like. that's literally the whole job. it goes and gets u bios page 2. main character energy tbh π
πΈ SYNOPSIS πΈ
int mpt3sas_config_get_bios_pg2 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , Mpi2BiosPage2_t *config_page );
look at that signature. three args, one int coming back at u. no notes π
π¦ ARGUMENTS π¦
iocβ the per adapter object. like, the whole vibe of this specific adapter lives in here πmpi_replyβ the reply mf payload that comes back from firmware. yes "mf" is doing real work in that sentence, it's a payload payload πconfig_pageβ the contents of the config page. this is where the good stuff lands β¨
π CONTEXT π
sleep.
that's it. that's the context. it sleeps, bestie. lowkey relatable π΄π€
β RETURN β
0 for success, non-zero for failure. classic. no cap, if u get a 0 ur slaying, anything else and it's a vibe check fail π
π SEE ALSO π
okay this is the long part and i'm not skipping ANY of it, we don't do that here. the kernel file is ./drivers/scsi/mpt3sas/mpt3sas_config.c and here's the whole friend group π
struct config_request(9)_config_display_some_debug(9)_config_alloc_config_dma_memory(9)_config_free_config_dma_memory(9)mpt3sas_config_done(9)_config_request(9)mpt3sas_config_get_manufacturing_pg0(9)mpt3sas_config_get_manufacturing_pg1(9)mpt3sas_config_get_manufacturing_pg10(9)mpt3sas_config_get_manufacturing_pg11(9)mpt3sas_config_set_manufacturing_pg11(9)mpt3sas_config_get_bios_pg3(9)mpt3sas_config_set_bios_pg4(9)mpt3sas_config_get_bios_pg4(9)mpt3sas_config_get_iounit_pg0(9)mpt3sas_config_get_iounit_pg1(9)mpt3sas_config_set_iounit_pg1(9)mpt3sas_config_get_iounit_pg3(9)mpt3sas_config_get_iounit_pg7(9)mpt3sas_config_get_iounit_pg8(9)mpt3sas_config_get_ioc_pg8(9)mpt3sas_config_get_ioc_pg1(9)mpt3sas_config_set_ioc_pg1(9)mpt3sas_config_get_sas_device_pg0(9)mpt3sas_config_get_pcie_device_pg0(9)mpt3sas_config_get_pcie_iounit_pg1(9)mpt3sas_config_get_pcie_device_pg2(9)mpt3sas_config_get_number_hba_phys(9)mpt3sas_config_get_sas_iounit_pg0(9)mpt3sas_config_get_sas_iounit_pg1(9)mpt3sas_config_set_sas_iounit_pg1(9)mpt3sas_config_get_expander_pg0(9)mpt3sas_config_get_expander_pg1(9)mpt3sas_config_get_enclosure_pg0(9)mpt3sas_config_get_phy_pg0(9)mpt3sas_config_get_phy_pg1(9)mpt3sas_config_get_raid_volume_pg1(9)mpt3sas_config_get_number_pds(9)mpt3sas_config_get_raid_volume_pg0(9)mpt3sas_config_get_phys_disk_pg0(9)mpt3sas_config_get_driver_trigger_pg0(9)_config_set_driver_trigger_pg0(9)mpt3sas_config_update_driver_trigger_pg0(9)mpt3sas_config_get_driver_trigger_pg1(9)_config_set_driver_trigger_pg1(9)mpt3sas_config_update_driver_trigger_pg1(9)mpt3sas_config_get_driver_trigger_pg2(9)_config_set_driver_trigger_pg2(9)mpt3sas_config_update_driver_trigger_pg2(9)mpt3sas_config_get_driver_trigger_pg3(9)_config_set_driver_trigger_pg3(9)mpt3sas_config_update_driver_trigger_pg3(9)mpt3sas_config_get_driver_trigger_pg4(9)_config_set_driver_trigger_pg4(9)mpt3sas_config_update_driver_trigger_pg4(9)mpt3sas_config_get_volume_handle(9)mpt3sas_config_get_volume_wwid(9)
like i said. whole friend group. ate and left no crumbs π
π« and that's the page, bestie π«
this one lives in ./drivers/scsi/mpt3sas (the source/version, yes ma'am π), dated October 2026, and the manual name is mpt3sas_config_get_bios_pg2(9). go get ur bios page 2, u got this πβ¨πΈ
π¦ 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