rproc_elf_get_boot_addr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rproc_elf_get_boot_addr β€” like, the Kernel API Manual page you actually wanna read ✨

okay so bestie, welcome to rproc_elf_get_boot_addr(9) from the Kernel API Manual β€” yes that manual, the one with all the ✨remoteproc✨ lore. this one's short and sweet, no cap πŸ“


🌸 NAME 🌸

rproc_elf_get_boot_addr β€” Get rproc's boot address. literally that's the whole job πŸ’…


✨ SYNOPSIS ✨

u64 rproc_elf_get_boot_addr (struct rproc *rproc , const struct firmware
       *fw );

like yes, she returns a u64, she's iconic like that πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • rproc β€” the remote processor handle 🫢 the main character of this whole situation
  • fw β€” the ELF firmware image 🌈 the actual blob of firmware vibes

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so important tea β˜•: the boot address is not a configurable property of all remote processors. nope. some of them will always boot at a specific hard-coded address, periodt. so don't go assuming you can just set it wherever you want, because the vibe check will fail 😭


πŸ’– RETURN πŸ’–

the entry point address of the ELF image πŸ”₯ that's the whole return value, slay


🌟 SEE ALSO 🌟

the whole remoteproc elf fam πŸ§šπŸ’œ


and that's the page!! shoutout to ./drivers/remoteproc for housing all this, dated October 2026, and yeah the footer says rproc_elf_get_boot_addr(9) because she's the moment πŸ’…βœ¨

πŸ“¦ where this page comes from