nvm_get_image(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nvm_get_image(9) β€” like, the whole image, bestie

Okay so real talk: this is a kernel API manual page β€” nvm_get_image(9), section 9, the driver/kernel-API girlies β€” and it does exactly one thing but it does it iconically. We're pulling a full image out of nvram. Not a peek, not a lil slice. The entire image. Periodt. 🫢


✨ NAME ✨

nvm_get_image β€” reads an entire image from nvram.

Like, all of it. The full thing. No cap. πŸŽ€


🌸 SYNOPSIS 🌸

int nvm_get_image (struct qed_dev *cdev , enum qed_nvm_images type , u8
*buf , u16 len );

She takes four arguments and returns an int. That's the whole vibe check. πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • cdev β€” Qed dev pointer. This is your main character: the device you're doing the thing to, bestie. πŸ”₯
  • type β€” type of the request nvram image. So like, which image you're asking for. She needs to know. πŸ™ˆ
  • buf β€” preallocated buffer to fill with the image. Key word: preallocated β€” you bring the bucket, she brings the water. You do not get to show up empty-handed. πŸ’€
  • len β€” length of the allocated buffer. Gotta tell her how much room you actually have, or it's giving chaos. ✨

πŸ‘‘ RETURN πŸ‘‘

0 on success, error otherwise. That's it, that's the whole story β€” zero is the slay, anything else is the group chat going quiet. 😭


🌈 SEE ALSO 🌈

The kernel file lives at ./include/linux/qed/qed_if.h, and here's the whole friend group, all present and accounted for β€” not one of them left on read:


Lowkey reminder: buf has to be preallocated and len has to be its actual length. She's trusting you on this one. Don't make it weird. 🧚

And that's the page, bestie β€” sourced from ./include/linux/qed, dated October 2026, filed under nvm_get_image(9). Go read an entire image. Slay. πŸ’…πŸ’œ

πŸ“¦ where this page comes from