fdt_create_with_flags(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– fdt_create_with_flags(9) β€” the kernel API manual, bestie edition ✨

okay so. you're about to make a brand-new fdt from scratch and you found fdt_create_with_flags β€” the section 9 kernel API manual page. slay. this is literally the first step of the sequential write interface, and honestly it's giving main character energy 🌟


🌸 NAME 🌸

fdt_create_with_flags β€” begin creation of a new fdt. that's it, that's the vibe πŸ’…


✨ SYNOPSIS ✨

int fdt_create_with_flags (void *buf , int bufsize , uint32_t flags );

πŸŽ€ ARGUMENTS πŸŽ€

  • buf β€” pointer to memory allocated where the fdt will be created. you gotta hand it a real spot in memory, bestie, no cap 🫢
  • bufsize β€” the size of the memory space at fdt. this is your budget, so know your limits fr fr πŸ“
  • flags β€” a valid combination of FDT_CREATE_FLAG_ flags, or 0. yes, 0 is a whole valid mood πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

fdt_create_with_flags begins the process of creating a new fdt with the sequential write interface. think of it as the "new document" button but for device trees ✨

the fdt creation process must end with fdt_finish to produce a valid fdt. don't ghost it halfway, okay? you have to call fdt_finish or it's literally not a valid fdt 😭


πŸ”₯ RETURN πŸ”₯

  • 0 β€” on success πŸ’–
  • -FDT_ERR_NOSPACE β€” bufsize is insufficient for a minimal fdt. your buffer said "too small, not today" πŸ’€
  • -FDT_ERR_BADFLAGS β€” flags is not valid. the flags didn't pass the vibe check πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./scripts/dtc/libfdt/libfdt.h β€” and bestie, there are so many friends in this group chat:

fdt_offset_ptr(9), fdt_next_tag(9), fdt_first_subnode(9), fdt_next_subnode(9), fdt_for_each_subnode(9), fdt_header_size(9), fdt_header_size_(9), fdt_check_header(9), fdt_move(9), fdt_check_full(9), fdt_get_string(9), fdt_string(9), fdt_find_max_phandle(9), fdt_get_max_phandle(9), fdt_generate_phandle(9), fdt_num_mem_rsv(9), fdt_get_mem_rsv(9), fdt_subnode_offset_namelen(9), fdt_subnode_offset(9), fdt_path_offset_namelen(9), fdt_path_offset(9), fdt_get_name(9), fdt_first_property_offset(9), fdt_next_property_offset(9), fdt_for_each_property_offset(9), fdt_get_property_by_offset(9), fdt_get_property_namelen(9), fdt_get_property(9), fdt_getprop_by_offset(9), fdt_getprop_namelen(9), fdt_getprop(9), fdt_get_phandle(9), fdt_get_alias_namelen(9), fdt_get_alias(9), fdt_get_symbol_namelen(9), fdt_get_symbol(9), fdt_get_path(9), fdt_supernode_atdepth_offset(9), fdt_node_depth(9), fdt_parent_offset(9), fdt_node_offset_by_prop_value(9), fdt_node_offset_by_phandle(9), fdt_node_check_compatible(9), fdt_node_offset_by_compatible(9), fdt_stringlist_contains(9), fdt_stringlist_count(9), fdt_stringlist_search(9), fdt_stringlist_get(9), FDT_MAX_NCELLS(9), fdt_address_cells(9), fdt_size_cells(9), fdt_setprop_inplace_namelen_partial(9), fdt_setprop_inplace(9), fdt_setprop_inplace_u32(9), fdt_setprop_inplace_u64(9), fdt_setprop_inplace_cell(9), fdt_nop_property(9), fdt_nop_node(9), fdt_create(9), fdt_resize(9), fdt_add_reservemap_entry(9), fdt_finish_reservemap(9), fdt_begin_node(9), fdt_property(9), fdt_property_placeholder(9), fdt_end_node(9), fdt_finish(9), fdt_create_empty_tree(9), fdt_open_into(9), fdt_pack(9), fdt_add_mem_rsv(9), fdt_del_mem_rsv(9), fdt_set_name(9), fdt_setprop_namelen(9), fdt_setprop(9), fdt_setprop_placeholder_namelen(9), fdt_setprop_placeholder(9), fdt_setprop_u32(9), fdt_setprop_u64(9), fdt_setprop_cell(9), fdt_setprop_string(9), fdt_setprop_namelen_string(9), fdt_setprop_empty(9), fdt_appendprop(9), fdt_appendprop_u32(9), fdt_appendprop_u64(9), fdt_appendprop_cell(9), fdt_appendprop_string(9), fdt_appendprop_addrrange(9), fdt_delprop(9), fdt_add_subnode_namelen(9), fdt_add_subnode(9), fdt_del_node(9), fdt_overlay_apply(9), fdt_overlay_target_offset(9), fdt_strerror(9)

iykyk πŸ’œ


this little love letter lives in ./scripts/dtc/libfdt, dated October 2026, and it's the fdt_create_with_flags(9) page from the Kernel API Manual. bye bestie, go build that fdt πŸ§šβ€β™€οΈπŸ’–

πŸ“¦ where this page comes from