mpi3mr_cfg_g..._io_unit_pg1(9)

📦 version 7.3.1, in nixpkgs unstable

💅 mpi3mr_cfg_get_sas_io_unit_pg1(9) 💅

okay so bestie, you've stumbled into the kernel API manual for mpi3mr_cfg_get_sas_io_unit_pg1 — yes that's the whole name, we're in section 9, kernel land, no cap. sit down, grab a strawberry 🍓, let's go.

✨ NAME ✨

mpi3mr_cfg_get_sas_io_unit_pg1 — literally reads the current SASIOUnit page1 for you. that's the whole vibe. 📖

🌸 SYNOPSIS 🌸

int mpi3mr_cfg_get_sas_io_unit_pg1 (struct mpi3mr_ioc *mrioc , struct
mpi3_sas_io_unit_page1 *sas_io_unit_pg1 , u16 pg_sz );

🎀 ARGUMENTS 🎀

  • mrioc — your adapter instance reference 💜 like, the whole controller you're talking to.
  • sas_io_unit_pg1 — pointer to where the SAS IO Unit page 1 gets returned 🫶 hand it a buffer, it hands you the page.
  • pg_sz — the size of the memory you allocated to that page pointer ✨ (u16, keep it cozy).

🦋 DESCRIPTION 🦋

so this one is the handler for the config page read for the SAS IO Unit page1, periodt. 💅 it does the read, then it checks ioc_status to decide whether the page read was a success or… not a success 😭. like a vibe check but for your config page.

🔥 RETURN 🔥

0 on success, non-zero on failure. that's it, that's the return. slay. 👑

👑 SEE ALSO 👑

the kernel file lives at ./drivers/scsi/mpi3mr/mpi3mr_fw.c — go say hi to it 🫶

and here's the whole friend group, the entire squad, not me listing them all but yes I am:

🫶 ok that's the whole page, every single one of those, iykyk. go read your config page and be iconic about it. 💖

cute little sign-off besties: this one's from ./drivers/scsi/mpi3mr, dated October 2026, and it's page mpi3mr_cfg_g..._io_unit_pg1(9) 🎀✨ love u, bye! 💜

📦 where this page comes from