fdt_appendprop_cell(9)
π¦ fdt_appendprop_cell β append a single cell value to a property π¦
okay bestie, so this one lives in the Kernel API Manual and it's genuinely one of the chillest little functions in libfdt. It's an alias, it appends a number, that's the whole vibe. Slay. β¨
β¨ SYNOPSIS β¨
int fdt_appendprop_cell (void *fdt , int nodeoffset , const char *name ,
uint32_t val );
like, yes, that's the whole signature, no cap π
π ARGUMENTS π
fdtβ pointer to the device tree blob π this is your tree, your main characternodeoffsetβ offset of the node whose property you wanna changenameβ name of the property you wanna changevalβ a 32-bit integer value to append to the property (native endian, so don't come at it with endian shenanigans, it's doing its own thing)
πΈ DESCRIPTION πΈ
So here's the tea: this is literally just an alternative name for fdt_appendprop_u32. That's it. That's the function. Same energy, different nickname. Not me finding out some of these are just aliases π
β RETURN β
0on success π she ate- a negative libfdt error value otherwise π so like, check your return value, please, i'm begging
π SEE ALSO π
The header where all the lore lives: Kernel file ./scripts/dtc/libfdt/libfdt.h. Then the whole extended friend group, in the order they showed up to the party π«Ά
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_with_flags(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_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)
ngl if you're here you probably actually wantedfdt_appendprop_u32(9)β same function, and honestly the_u32name is the one that gets invited to more parties. iykyk π
okay that's the whole page bestie, go append your cells π this lil writeup came to you from ./scripts/dtc/libfdt, dated October 2026, filed under fdt_appendprop_cell(9) β mwah, stan, bye ππ§
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms