fdt_get_property(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

okay bestie, this is fdt_get_property(9) from the Kernel API Manual — and the whole vibe is: fdt_get_property — find a given property in a given node. periodt 💅

✨ SYNOPSIS ✨

const struct fdt_property * fdt_get_property (const void *fdt , int
nodeoffset , const char *name , int *lenp );

🎀 ARGUMENTS 🎀

  • fdt — pointer to the device tree blob, aka the whole tree bestie 🫶
  • nodeoffset — offset of the node whose property to find ✨
  • name — name of the property to find, literally the string we're hunting 🔍
  • lenp — pointer to an integer variable (will be overwritten) or NULL — yes, it gets overwritten, don't be shocked 💀

🌸 DESCRIPTION 🌸

okay so fdt_get_property retrieves a pointer to the fdt_property structure within the device tree blob corresponding to the property named 'name' of the node at offset nodeoffset. If lenp is non-NULL, the length of the property value is also returned, in the integer pointed to by lenp. that's the whole quest, bestie 🧚✨

🔥 RETURN 🔥

here's the return tea ☕️:

  • on success: pointer to the structure representing the property — if lenp is non-NULL, *lenp contains the length of the property value (>=0) 💖
  • NULL, on error — if lenp is non-NULL, *lenp contains an error code (<0):
    • -FDT_ERR_NOTFOUND — node does not have named property
    • -FDT_ERR_BADOFFSET — nodeoffset did not point to FDT_BEGIN_NODE tag
    • -FDT_ERR_BADMAGIC, -FDT_ERR_BADVERSION, -FDT_ERR_BADSTATE, -FDT_ERR_BADSTRUCTURE, -FDT_ERR_TRUNCATED — standard meanings
heads up bestie: if you pass lenp, it absolutely gets overwritten. that's not a drill 💅

🦋 SEE ALSO 🦋

Kernel file: ./scripts/dtc/libfdt/libfdt.h

the whole fdt bestie squad is here, no cap:

and that's the tea ☕️ — this iconic lil page lives in ./scripts/dtc/libfdt, dated October 2026, and it's still serving fdt_get_property(9) realness. mwah 💋

📦 where this page comes from