fdt_get_property_namelen(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– fdt_get_property_namelen(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for fdt_get_property_namelen, and it is literally about find a property based on substring. yes we are in kernel-dev (9) territory, we are fabulous, and we are matching only the first namelen characters of a name. no cap. 🫢


✨ NAME ✨

fdt_get_property_namelen β€” find a property based on substring. that’s the whole vibe: property hunt, but make it substring. πŸ”Ž


πŸ“œ SYNOPSIS πŸ“œ

here’s the signature, exactly, because we do not mess with code in this house:

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

πŸŽ€ ARGUMENTS πŸŽ€

  • fdt β€” pointer to the device tree blob. yep, the blob itself. 🧚
  • nodeoffset β€” offset of the node whose property to find. like, which node are we snooping in? πŸ‘€
  • name β€” name of the property to find. the property’s name, bestie.
  • namelen β€” number of characters of name to consider. so we are only checking the first namelen chars, periodt. ✨
  • lenp β€” pointer to an integer variable (will be overwritten) or NULL. yes it gets overwritten, do not clutch your old value. 😭

πŸ¦‹ DESCRIPTION πŸ¦‹

This is identical to fdt_get_property, but only examine the first namelen characters of name for matching the property name. that’s it, that’s the whole plot. it’s giving β€œsame function, shorter name check.” πŸ’…


πŸ”₯ RETURN πŸ”₯

pointer to the structure representing the property, or NULL if not found. so like, if it’s not there, you get NULL, no drama. if it is, you get the pointer. iconic. πŸ‘‘


🌈 SEE ALSO 🌈

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

and then the whole friend group, all of them, no skips:


that’s the whole page, bestie. signed with sparkle from source/version ./scripts/dtc/libfdt, dated October 2026, for fdt_get_property_namelen(9). now go find that property substring, slay, and hydrate. πŸ’–βœ¨πŸ’…

πŸ“¦ where this page comes from