gsm_dlci_data(9)

📦 version 7.3.1, in nixpkgs unstable

okay so bestie — welcome to gsm_dlci_data(9), straight out of the Kernel API Manual (the 9 is the section number, we love a numbered girlie ✨). This one's short, sweet, and honestly kind of iconic: it's the little function that catches data when a frame rolls in. Let's get into it 🫶

🎀 NAME 🎀

gsm_dlci_data — data arrived 💌

Like, literally that's the whole vibe. Data showed up. The function is here for it.

✨ SYNOPSIS ✨

void gsm_dlci_data (struct gsm_dlci *dlci , const u8 *data , int clen );

No return value, no drama — void queen behavior, we love to see it 👑

🦋 ARGUMENTS 🦋

  • dlci — the channel 💅 this is the whole point, the channel the data belongs to
  • data — the block of bytes received 🍓 a big lil pile of raw bytes
  • clen — the length of that received block 📏 so we know how many bytes we're working with, no guessing

🌸 DESCRIPTION 🌸

So here's the tea ☕ — a UI or UIH frame has arrived, and it's carrying data for a channel that is not the control channel. Main character data energy, honestly.

Then it's basically a vibe check on the virtual tty:

  • if the relevant virtual tty is open, we shovel the bits down it 🚀 (yes, "shovel" is the technical term, periodt)
  • if it is not open, we drop them 💀 no tty, no home, bye bestie

That's it. That's the function. Zero notes, ate and left no crumbs 🔥

💜 SEE ALSO 💜

Kernel file ./drivers/tty/n_gsm.c — the mothership the whole GSM mux family lives in 🌈 and here's the full squad, because every single one of them is a reference and we do not leave anybody out of the group chat:

and that's the whole friend group 🧚💖

ngl bestie, this page came from ./drivers/tty and it's dated October 2026, courtesy of the Kernel API Manual. so when you cite it, cite it with your whole chest 💅🎀🦋 slay, and good luck out there with your frames ✨
📦 where this page comes from