request_par...are_into_buf(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

�✨ request_partial_firmware_into_buf βœ¨πŸ’Ύ

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” yes we're literally in the kernel docs, stay with me, this one's actually cute and short.


πŸ’… NAME πŸ’…

request_partial_firmware_into_buf β€” load partial firmware into a buffer you already allocated, no cap 🫢


🌸 SYNOPSIS 🌸

int request_partial_firmware_into_buf (const struct firmware **firmware_p , const char *name , struct device *device , void *buf , size_t size , size_t offset );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • firmware_p β€” pointer to the firmware image, bestie. it's a double pointer, she's fancy πŸ’…
  • name β€” the name of the firmware file, iykyk πŸ—‚οΈ
  • device β€” the device this firmware is being loaded for, and also the one the DMA region got allocated for 🫢
  • buf β€” address of the buffer you're loading the firmware into πŸ“¦
  • size β€” the size of that buffer, keep it accurate fr fr πŸ“
  • offset β€” the offset into the file to read from, like you're skipping ahead in a playlist ⏩

πŸ‘‘ DESCRIPTION πŸ‘‘

so this one works pretty much exactly like request_firmware_into_buf β€” like, same energy, same vibe β€” except it lets you do a partial read of the file. not the whole thing, just a lil slice ✨ iconic behavior honestly.


🌈 SEE ALSO 🌈

kernel file ./drivers/base/firmware_loader/main.c β€” go read the source, it's giving main character energy πŸ“–

and the whole firmware-loader friend group, in this exact order:


πŸ’€ reminder that this whole page lives in ./drivers/base/firmware_loader, and it's dated October 2026 β€” yes, future girlie behavior πŸ§šβ€β™€οΈ

k that's the whole page, mwah, go load some partial firmware πŸ“πŸ’œ β€” request_par...are_into_buf(9) signing off πŸŽ€

πŸ“¦ where this page comes from