mpt3sas_con...cturing_pg11(9)
πΈ mpt3sas_con...cturing_pg11(9) πΈ
okay so bestie, this page lives in the Kernel API Manual, and the actual function is mpt3sas_config_get_manufacturing_pg11 β it's the one that goes and obtains manufacturing page 11. no cap, that's the whole quest. π
β¨
β¨ NAME β¨
mpt3sas_config_get_manufacturing_pg11 β obtain manufacturing page 11 π
π«Ά SYNOPSIS π«Ά
int mpt3sas_config_get_manufacturing_pg11 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , struct Mpi2ManufacturingPage11_t
*config_page );
π ARGUMENTS π
iocβ per adapter object. like, the adapter's whole little world π¦mpi_replyβ reply mf payload returned from firmware. that's the firmware's comeback message πconfig_pageβ contents of the config page. this is where the page contents go, periodt π
π΄ CONTEXT π΄
sleep. yep, that's the context note β literally just sleep. that's the tea. βπ
π₯ RETURN π₯
0 for success, non-zero for failure. slay if it's 0, otherwise it's a nope β¨
π SEE ALSO π
the whole friend group, assembled:
- Kernel file:
./drivers/scsi/mpt3sas/mpt3sas_config.c - Struct:
struct config_request(9) - Config helpers:
_config_display_some_debug(9),_config_alloc_config_dma_memory(9),_config_free_config_dma_memory(9),mpt3sas_config_done(9),_config_request(9) - Manufacturing pages:
mpt3sas_config_get_manufacturing_pg0(9),mpt3sas_config_get_manufacturing_pg1(9),mpt3sas_config_get_manufacturing_pg10(9),mpt3sas_config_set_manufacturing_pg11(9) - BIOS pages:
mpt3sas_config_get_bios_pg2(9),mpt3sas_config_get_bios_pg3(9),mpt3sas_config_set_bios_pg4(9),mpt3sas_config_get_bios_pg4(9) - IOUnit pages:
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) - IOC pages:
mpt3sas_config_get_ioc_pg8(9),mpt3sas_config_get_ioc_pg1(9),mpt3sas_config_set_ioc_pg1(9) - SAS/PCIe device pages:
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) - HBA phys / SAS IOUnit:
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) - Expander / enclosure / phy:
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) - RAID volume / PDS / phys disk:
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) - Driver trigger pages:
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) - Volume handle / wwid:
mpt3sas_config_get_volume_handle(9),mpt3sas_config_get_volume_wwid(9)
cute lil sign-off tea β: this one comes from ./drivers/scsi/mpt3sas, October 2026 edition β that's the source/version + date combo at the bottom, bestie. mwah πβ¨
π¦ 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