gsm_control_command(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« gsm_control_command(9) β€” kernel API manual energy ✨

okay so bestie, welcome to gsm_control_command from the Kernel API Manual β€” she's a function, she's in section 9, and she's literally the one who ships your command frame off to a control. no cap, that's the whole vibe. πŸŽ€


✨ NAME ✨

gsm_control_command β€” send a command frame to a control πŸ¦‹


🌸 SYNOPSIS 🌸

int gsm_control_command (struct gsm_mux *gsm , int cmd , const u8 *data
, int dlen );

πŸ’œ ARGUMENTS πŸ’œ

  • gsm β€” the gsm channel πŸ’… that's your mux, your main character.
  • cmd β€” the command to use πŸ‘‘ like, which command are we actually sending, bestie?
  • data β€” data to follow encoded info πŸ“ the payload that rides along after the encoded bits.
  • dlen β€” length of data πŸ“ how many bytes of that data we're working with. don't get it wrong, iykyk.

πŸ”₯ DESCRIPTION πŸ”₯

Encode up and queue a UI/UIH frame containing our command. that's it, that's the whole job ✨ β€” she encodes it, she queues it, she slays. periodt. πŸ’…


🌈 SEE ALSO 🌈

Kernel file ./drivers/tty/n_gsm.c β€” and honestly the whole gsm friend group came through, so let's give them their moment 🫢:


and that's the page, bestie!! 🧚 before you go β€” this one came out of ./drivers/tty, dated October 2026, and yes, the page is literally named gsm_control_command(9) too, she's consistent like that πŸ’– mwah, go read some kernel source, ily πŸ’œβ­

πŸ“¦ where this page comes from