gsm_queue(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so this is the glow-up of the gsm_queue(9) page from the Kernel API Manual, and it's short but it eats. it's giving "one function, huge responsibilities." let's get into it πŸŽ€


✨ NAME ✨

gsm_queue β€” a GSM frame is ready to process πŸ¦‹

like, the frame has arrived and it's your turn to deal with it. main character frame energy.


✨ SYNOPSIS ✨

void gsm_queue (struct gsm_mux *gsm );

that's it. that's the whole call. returns void, so no little treat at the end, sorry 😭


✨ ARGUMENTS ✨

  • gsm β€” pointer to our gsm mux 🫢 literally our mux, ours, the one we're working with.

✨ DESCRIPTION ✨

so picture this: at this point in time, a frame has arrived and been demangled from the line encoding 🌸. all the differences between the encodings have already been handled below us (not our problem, slay), and the frame is unpacked into the structures ✨.

now the part you need to remember, no cap: the fcs holds the header FCS, but any data FCS must be added here πŸ‘‘. so if you were hoping to skip that, nope, that's literally your job in this function. the header FCS is already cozy in fcs, the data FCS is not, and it goes in right here. periodt πŸ’…

lowkey important: the fcs only covers the header. the data FCS is on you. don't forget it πŸ™ˆ

✨ SEE ALSO ✨

the whole friend group 🫢 these are all from the kernel file ./drivers/tty/n_gsm.c:

the fcs + parsing girlies

encoding + params icons

device registration squad

packets, printing, and stuffing

queueing besties

dlci data output crew

control message gang

dlci lifecycle girlies (open, close, negotiate, repeat)

timers + config crew

dlci memory besties

the receive-state fixers

mux management squad

the gsmld collective

modem updates, the finale


that's the whole list, nothing skipped, i checked twice πŸ’– and that's the vibe: ./drivers/tty, October 2026. go add that data FCS bestie, ily, bye πŸ§šβœ¨πŸ’œ

πŸ“¦ where this page comes from