ubi_get_vid_hdr(9)
π ubi_get_vid_hdr(9) β the Kernel API Manual, bestie edition β¨
okay so real talk, this is the manual page for ubi_get_vid_hdr from the Kernel API Manual, and it is genuinely so simple it's almost suspicious π«Ά
πΈ NAME πΈ
ubi_get_vid_hdr β get the VID header attached to a VID buffer π
like, that's the whole gig. it gets the VID header. from a VID buffer. no cap. β¨
π SYNOPSIS π
struct ubi_vid_hdr * ubi_get_vid_hdr (struct ubi_vid_io_buf *vidb );
that's the entire call, character for character, do not come for me about the spacing π
π¦ ARGUMENTS π¦
vidbβ the VID buffer π literally just the VID buffer, that's the whole input, she's low maintenance
β SEE ALSO β
so if you wanna go down the rabbit hole (and you should, bestie, it's giving main character energy π), the kernel file is ./drivers/mtd/ubi/ubi.h and it's got the whole friend group in there:
struct ubi_vid_io_buf(9)struct ubi_wl_entry(9)struct ubi_ltree_entry(9)struct ubi_rename_entry(9)struct ubi_fastmap_layout(9)struct ubi_fm_pool(9)struct ubi_eba_leb_desc(9)struct ubi_volume(9)struct ubi_volume_desc(9)struct ubi_debug_info(9)struct ubi_device(9)struct ubi_ainf_peb(9)struct ubi_ainf_volume(9)struct ubi_attach_info(9)struct ubi_work(9)ubi_init_vid_buf(9)ubi_free_vid_buf(9)ubi_ro_mode(9)vol_id2idx(9)idx2vol_id(9)ubi_is_fm_vol(9)ubi_find_fm_block(9)
ngo look at all those structs, an entire squad ππ
ok that's genuinely everything this page has to give, she's short and she knows it, and honestly? iconic. π
and that's a wrap, bestie β this one comes from ./drivers/mtd/ubi, dated October 2026, filed under ubi_get_vid_hdr(9). slay, go read the header file π
β¨π§
π¦ 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