yamon_dt_append_memory(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… yamon_dt_append_memory β€” bestie edition πŸŽ€

okay so this is from the Kernel API Manual, section 9, and the function is literally called yamon_dt_append_memory. say it with me: yamon_dt_append_memory. iconic name, no notes ✨


🌸 NAME 🌸

yamon_dt_append_memory β€” append YAMON-provided memory info to /memory 🫢


πŸ’– SYNOPSIS πŸ’–

int yamon_dt_append_memory (void *fdt , const struct yamon_mem_region
*regions );

like yes bestie we're calling it with an fdt and a regions pointer, keep up πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • fdt β€” the FDT blob. that's the whole vibe. 🧚
  • regions β€” a zero size terminated array of physical memory regions. yes, the termination is a zero size, don't forget it or it's giving infinite loop energy 😭

✨ DESCRIPTION ✨

So what it does is generate a /memory node in fdt, based upon memory size information provided by YAMON in its environment and the regions array. both. together. slay πŸ’œ

Literally the whole job is: YAMON says how much memory, you hand over your regions, and boom β€” /memory node gets generated in the fdt. periodt.


πŸ”₯ RETURN πŸ”₯

0 on success, else -errno. that's it, that's the return value. negative errno is the "something went wrong bestie" signal πŸ’€


🌈 SEE ALSO 🌈

go read those too, iykyk πŸ‘‘


fr fr the details above are the whole page β€” nothing extra, nothing missing πŸ’–

and that's a wrap, bestie! written from ./arch/mips/include/asm, dated October 2026, and yes the page is literally named yamon_dt_append_memory(9) β€” go off, kernel docs πŸ’…πŸŽ€πŸŒΈ

πŸ“¦ where this page comes from