gsm_dlci_command(9)

📦 version 7.3.1, in nixpkgs unstable

💅 gsm_dlci_command — data arrived on control channel

okay bestie, so you're reading the man page for gsm_dlci_command from the Kernel API Manual (section 9, the kernel-api girlies 💖), and honestly? it's a little function with a big job. let's get into it.

✨ SYNOPSIS ✨

void gsm_dlci_command (struct gsm_dlci *dlci , const u8 *data , int len );

that's it. that's the whole signature. no return value, no drama, just vibes and a pointer. 🫶

🎀 ARGUMENTS 🎀

  • dlci — the channel. like, the actual DLCI struct you're working with. main character energy tbh.
  • data — the block of bytes that just showed up. yep, raw bytes, freshly received 💅
  • len — the length of that received block. gotta know how much you got, periodt.

🌸 DESCRIPTION 🌸

lowkey the whole point: a UI or UIH frame has arrived, and it's carrying data for DLCI 0, aka the control channel 👑. so like, this is the control channel specifically — not your data channels, bestie, keep up.

inside that frame there should be a command EA, followed by control data bytes. and here's the iconic part: the command EA contains a command/response bit, and we divide up the work accordingly. that bit is basically the vibe check for the whole frame — it tells you which way the traffic is flowing, so you know what to do next. 🔥

ngl there's no return value here, so if you were waiting for a status code... she's not coming. the function just does the thing. 🙈

🦋 SEE ALSO 🦋

the kernel file ./drivers/tty/n_gsm.c and, fr fr, a whole friend group of functions — go say hi:

like I said. a whole friend group. ✨

and that's the page, bestie!! 🎀 this one lives in ./drivers/tty (yes, the drivers/tty girlies ate), dated October 2026, and it's filed as gsm_dlci_command(9) in the Kernel API Manual. mwah 💋 go read n_gsm.c and slay. 💜

📦 where this page comes from