of_fdt_is_compatible(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– of_fdt_is_compatible(9) πŸ’–

okay so bestie, welcome to the of_fdt_is_compatible(9) page β€” it lives in the Kernel API Manual and honestly it's giving tiny-but-mighty energy. it does exactly one thing and it does it well: it tells you whether a given node (from a given blob) has your compat string chilling in its compatible list. that's it. that's the whole personality. πŸŽ€


✨ NAME ✨

of_fdt_is_compatible β€” return true if the given node from the given blob has compat in its compatible list. no cap, that's literally the job πŸ’…


🌸 SYNOPSIS 🌸

int of_fdt_is_compatible (const void *blob , unsigned long node , const
char *compat );

like… it's a function. it takes three things. it returns an int. we love a low-drama signature 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • blob β€” a device tree blob. yes, the whole blob. it's the vibe provider for everything else here πŸ’–
  • node β€” the node to test. this is the one we're putting under the microscope, slay πŸ”
  • compat β€” the compatible string to compare with the compatible list. this is your search term, your main character string πŸ‘‘

⭐ RETURN ⭐

it returns a non-zero value on match β€” and here's the cute part: smaller values are returned for more specific compatible values. so the number isn't just "yes", it's "yes and here's how specific it is". iykyk 🌈


🧚 SEE ALSO 🧚

okay this list is lowkey a whole friend group, get comfy:

go read them. they're all iconic in their own way, fr fr πŸ‘‘πŸ’œ


πŸ’€ reminder that this page is sourced from ./drivers/of β€” that's where all the flat-device-tree lore lives πŸ“

and that's a wrap bestie!! this one's dated October 2026, sourced from ./drivers/of, and yes the page name is literally of_fdt_is_compatible(9) β€” drink some water, go read ./drivers/of/fdt.c, and slay your device tree πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from