STRUCT VIVALDI_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct vivaldi_data(9) β€” from the Kernel API Manual, bestie

okay so picture this: it's a manual page for struct vivaldi_data(9), and it lives in the Kernel API Manual. that's the vibe. it's all about function row map data for ChromeOS Vivaldi keyboards 🎹✨ β€” and honestly? it's giving "small struct, big responsibility."


🌸 SYNOPSIS 🌸

here's the whole entire struct, no cap, exactly as it is:

struct vivaldi_data {
    u32 function_row_physmap[VIVALDI_MAX_FUNCTION_ROW_KEYS];
    unsigned int num_function_row_keys;
 };

two members. that's it. that's the whole queen. πŸ‘‘


πŸŽ€ Members πŸŽ€

✨ function_row_physmap

bestie this one is an array β€” of scancodes, or whatever the equivalent is for your setup (HID usage codes, encoded rows/columns, etc β€” the manpage lists all three, i'm not picking favorites πŸ’–). it holds the top row function keys, and the order is left to right, exactly like you'd read them on the keyboard. iconic behavior, honestly.

✨ num_function_row_keys

this one's an unsigned int, and it's just... the number. the count. how many top row keys your custom keyboard actually has. that's the whole job. 🫢


🌈 Description 🌈

so the lore is: this structure is supposed to be used by ChromeOS keyboards that are rocking the Vivaldi keyboard function row design. that's the intended use case, fr fr β€” that's what it's here for. πŸ¦‹


πŸ‘‘ SEE ALSO πŸ‘‘

  • Kernel file ./include/linux/input/vivaldi-fmap.h β€” go read it, iykyk πŸ’…

πŸ’€ one tiny thing: don't come for me if you're looking for extra behavior notes, because the original page doesn't give any. this struct tells you what it holds and who it's for, and politely leaves it at that. periodt.

mwah, that's a wrap πŸ’– this lil page came from ./include/linux/input and it's dated October 2026 β€” so yeah, go forth and map those function rows, bestie. πŸŒŸπŸŽ€πŸŒ·

πŸ“¦ where this page comes from