fdt_check_full(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ fdt_check_full πŸ’…

okay so bestie, welcome to fdt_check_full(9) β€” a page straight out of the Kernel API Manual, and she is the vibe check for your device tree. 🌸


πŸ’– NAME

fdt_check_full β€” check device tree validity ✨


πŸŽ€ SYNOPSIS

int fdt_check_full (const void *fdt , size_t bufsize );

like literally that's the whole function signature, no cap 🫢


πŸ¦‹ ARGUMENTS

  • fdt β€” pointer to the device tree blob. yes, that blob. the flattened one. πŸ‘‘
  • bufsize β€” size of the buffer containing the device tree. gotta tell her how much room she's working with πŸŽ€

🌈 DESCRIPTION

okay so fdt_check_full checks that the given buffer contains a valid flattened device tree and that the tree structure is internally consistent. πŸ”₯

this is a more thorough check than fdt_check_header, bestie. like, fdt_check_header glances at the outfit, and fdt_check_full does the full mirror check, the spin, the lighting test, all of it. πŸ’…βœ¨


⭐ RETURN

  • 0 β€” on success, slay πŸ’–
  • -FDT_ERR_BADMAGIC
  • -FDT_ERR_BADVERSION
  • -FDT_ERR_BADSTATE
  • -FDT_ERR_BADSTRUCTURE
  • -FDT_ERR_TRUNCATED

these are all standard meanings, iykyk 😭


🧚 SEE ALSO

okay this is the whole group chat, buckle up πŸ“


ok and one last thing β€” this whole page lives under ./scripts/dtc/libfdt, and it's dated October 2026. so yeah, she's from the future and she's still iconic. periodt. πŸ’œπŸŽ€βœ¨
πŸ“¦ where this page comes from