mpt3sas_con...cturing_pg10(9)
π mpt3sas_con...cturing_pg10(9) β like, the actual man page β¨
okay bestie, so this is page 9 of the Kernel API Manual and the title got literally cut off mid-word (mpt3sas_con...cturing_pg10(9), iconic behavior honestly), but the vibe is clear: we're getting the manufacturing page 10 out of your mpt3sas adapter. no cap. π
β¨ NAME β¨
mpt3sas_config_get_manufacturing_pg10 β obtain manufacturing page 10 π§
πΈ SYNOPSIS πΈ
int mpt3sas_config_get_manufacturing_pg10 (struct MPT3SAS_ADAPTER *ioc ,
Mpi2ConfigReply_t *mpi_reply , struct Mpi2ManufacturingPage10_t
*config_page );
π ARGUMENTS π
iocβ the per adapter object, aka your main character πmpi_replyβ the reply mf payload the firmware hands back to you π«Άconfig_pageβ the contents of the config page, right there π
π¦ CONTEXT π¦
sleep. π΄
like, actually β this one sleeps. plan for it.
π RETURN π
0 for success, non-zero for failure. that's it, that's the whole mood fr fr π
π SEE ALSO π
Kernel file: ./drivers/scsi/mpt3sas/mpt3sas_config.c β that's where all the lore lives, iykyk π
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_pg11(9)mpt3sas_config_set_manufacturing_pg11(9)mpt3sas_config_get_bios_pg2(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)
that's a whole friend group right there, and you're gonna want to know every single one of them π«Ά
that's the whole page bestie!! sourced from ./drivers/scsi/mpt3sas, dated October 2026, living in the Kernel API Manual β go read it again if you need to, i'll wait πβ¨
π¦ 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