gsm_dlci_begin_open(9)

📦 version 7.3.1, in nixpkgs unstable

💅 gsm_dlci_begin_open — the Kernel API Manual tea ☕✨

okay so bestie, this one lives in the kernel API manual (gsm_dlci_begin_open(9) — section 9, we love a man page moment) and it's literally the "hey, open this channel" button. let's get into it 🫶

✨ NAME ✨

gsm_dlci_begin_open — start channel open procedure 🔥

🌸 SYNOPSIS 🌸

void gsm_dlci_begin_open (struct gsm_dlci *dlci );

no cap, that's the whole signature. void in, no return value out, it's giving "trust the process" energy 💅

🎀 ARGUMENTS 🎀

  • dlci — the DLCI you wanna open. that's it. that's the argument. the DLCI to open, periodt. 🦋

👑 DESCRIPTION 👑

okay so here's the vibe 👇

we're commencing the opening of a DLCI, and we're doing it from the Linux side. like, we start it. we're the main character here.

we issue SABM messages to the modem 📨, and the modem should then reply with a UA or an ADM. the moment one of those lands, we move into open state. slay, transition complete ✨

and the way this happens is asynchronously — literally not blocking, we're not sitting around waiting like 😭 — with retry running off timers and the responses. so the whole thing is vibing on a timer loop and reacting to what comes back. 🔁

also, parameter negotiation is performed before SABM if required. only if required tho. iykyk 🧚

💖 SEE ALSO 💖

Kernel file ./drivers/tty/n_gsm.c — that's the home base bestie, everything below lives in that neighborhood 🏡

like, that's a whole friend group and they're all iconic 💜 go read them, i'm begging 🥺

💀 quick reminder bestie: this returns void, so there's no return value to check. the "did it open" answer comes later, through the async timers and the modem's UA or ADM reply. don't go looking for an int that isn't there, i'm gonna cry 😭

and that's the page!! 🎀 from the fine folks over at ./drivers/tty 🌈, dated October 2026 — mwah, sending you all the kernel kisses, drink some water, close your DLCIs responsibly ✨💅🫶

📦 where this page comes from