firmware_req..._builtin_buf(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… firmware_req..._builtin_buf(9) β€” Kernel API Manual

okay so bestie, welcome to the glow-up era of firmware loading ✨ this one's from the Kernel API Manual, and it's genuinely one of the more chill functions you'll meet. no cap.


🌸 NAME

firmware_request_builtin_buf β€” load builtin firmware into optional buffer πŸŽ€


πŸ¦‹ SYNOPSIS

bool firmware_request_builtin_buf (struct firmware *fw , const char *name , void *buf , size_t size );

like, yes, it returns a bool. keep that in mind, it matters later πŸ’…


πŸ‘‘ ARGUMENTS

  • fw β€” pointer to the firmware struct. your main character, the thing that gets filled in 🫢
  • name β€” name of the firmware file. literally just the name, that's the whole vibe ✨
  • buf β€” if you set this, it lets you use a pre-allocated buffer so that the built-in firmware gets copied into it. this field can be NULL, which is very much allowed, no stress 🌈. it's used by callers such as request_firmware_into_buf and request_partial_firmware_into_buf β€” iykyk 🧚
  • size β€” if buf was provided, this is the max size of the allocated buffer available. and bestie, listen: if the built-in firmware does not fit into the pre-allocated buf, this call will fail πŸ’€ no negotiating. it either fits or it doesn't.

πŸ”₯ DESCRIPTION

So like, what does it even do πŸ’– β€” it looks for the firmware in the built-in kernel. Only if the kernel was built-in with the firmware you're looking for will this call possibly succeed. that "possibly" is doing a lot of heavy lifting, ngl πŸ™ˆ

and if you passed a buf, the firmware will be copied into it iff the built-in firmware fits into the pre-allocated buffer size specified in size. yes, iff. that's not a typo, that's just how it is πŸ’…

⚠️ heads up bestie: this caller is to be used internally by the firmware_loader only. so like, don't be out here calling it from random places, okay? that's not the vibe check you want to fail 🌸

πŸ’œ SEE ALSO


okay that's the whole page, periodt πŸ’…πŸ¦‹

sign-off besties: this one comes from ./drivers/base/firmware_loader... and it's dated October 2026 β€” iconic of it honestly, and it's still filed under firmware_req..._builtin_buf(9) if you need to find it again πŸŒŸπŸŽ€

πŸ“¦ where this page comes from