gsm_data_alloc(9)

📦 version 7.3.1, in nixpkgs unstable

💅 gsm_data_alloc(9) — the Kernel API Manual glow-up 🎀

okay so this is a page from the Kernel API Manual, it's gsm_data_alloc(9), and bestie, it's literally about making a data frame out of thin air. let's get into it ✨

🌸 NAME 🌸

gsm_data_alloc — allocate data frame 🦋

✨ SYNOPSIS ✨

struct gsm_msg * gsm_data_alloc (struct gsm_mux *gsm , u8 addr , int len
, u8 ctrl );

like, that's the whole signature, no cap. four args, one pointer back. periodt 💅

🫶 ARGUMENTS 🫶

  • gsm — the GSM mux. it's giving "the whole vibe container" 💖
  • addr — the DLCI address, iconic little identifier 🎀
  • len — the length, and hear me out: this is length excluding header and FCS. do NOT count those. i'm serious 🙈
  • ctrl — the control byte, tiny but main character energy ⭐

🔥 DESCRIPTION 🔥

so what it does is allocate a brand-new data buffer for sending frames that have data in them. literally that's it, that's the job 🌈

here's the lil detail that matters though: space is left at the front for header bytes 👑. but — and this is the important part — that's treated as an implementation detail and it is not for the high level code to use. so don't touch it, don't peek at it, don't build your whole personality on it. iykyk 💀

🦋 SEE ALSO 🦋

Kernel file ./drivers/tty/n_gsm.c — and honestly the whole friend group is here, so let me introduce everyone 💜:

like, the whole roster. ate and left no crumbs 👑

ngl bestie, that's the entire page — no hidden lore, no extra flags, nothing sneaky hiding in the fine print 🍓

and that's the wrap, fr fr 💖 this one came out of ./drivers/tty and it's dated October 2026 — mwah, stan, no notes, see u in the next page 🧚‍♀️🌈💜

📦 where this page comes from