gsm_send(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

Okay so picture this: it's giving kernel-doc, it's giving TTY driver energy, and it's literally the page for gsm_send. Welcome to the group chat, pull up a chair πŸ¦‹


✨ NAME ✨

gsm_send β€” send a control frame πŸ’Œ


🌸 SYNOPSIS 🌸

int gsm_send (struct gsm_mux *gsm , int addr , int cr , int control );

πŸŽ€ ARGUMENTS πŸŽ€

  • gsm β€” our GSM mux πŸ‘‘ (the one we're working with, our main character)
  • addr β€” the address for the control frame πŸ“¬
  • cr β€” the command/response bit, seen as initiator 🫑
  • control β€” the control byte, including the PF bit 🧚

πŸ’– DESCRIPTION πŸ’–

So what this does is: it formats up and transmits a control frame. That's the whole vibe, no cap ✨

And here's the little note that matters: these should be transmitted ahead of data when they are needed. Like, control frame goes first, data knows its place πŸ’…


🌈 SEE ALSO 🌈

Kernel file ./drivers/tty/n_gsm.c β€” and honestly the whole n_gsm extended family showed up to the party, obsessed πŸ“

gsm_fcs_add(9), gsm_fcs_add_block(9), gsm_read_ea(9), gsm_read_ea_val(9), gsm_encode_modem(9), gsm_encode_params(9), gsm_register_devices(9), gsm_unregister_devices(9), gsm_print_packet(9), gsm_stuff_frame(9), gsm_dlci_clear_queues(9), gsm_response(9), gsm_command(9), gsm_data_alloc(9), gsm_send_packet(9), gsm_is_flow_ctrl_msg(9), gsm_data_kick(9), __gsm_data_queue(9), gsm_data_queue(9), gsm_dlci_data_output(9), gsm_dlci_data_output_framed(9), gsm_dlci_modem_output(9), gsm_dlci_data_sweep(9), gsm_dlci_data_kick(9), gsm_control_command(9), gsm_control_reply(9), gsm_process_modem(9), gsm_process_negotiation(9), gsm_control_modem(9), gsm_control_negotiation(9), gsm_control_rls(9), gsm_control_message(9), gsm_control_response(9), gsm_control_keep_alive(9), gsm_control_transmit(9), gsm_control_retransmit(9), gsm_control_send(9), gsm_control_wait(9), gsm_dlci_close(9), gsm_dlci_open(9), gsm_dlci_negotiate(9), gsm_dlci_t1(9), gsm_dlci_begin_open(9), gsm_dlci_set_opening(9), gsm_dlci_set_wait_config(9), gsm_dlci_begin_close(9), gsm_dlci_data(9), gsm_dlci_command(9), gsm_kick_timer(9), gsm_dlci_copy_config_values(9), gsm_dlci_config(9), gsm_dlci_alloc(9), gsm_dlci_free(9), gsm_dlci_release(9), gsm_queue(9), gsm0_receive_state_check_and_fix(9), gsm0_receive(9), gsm1_receive_state_check_and_fix(9), gsm1_receive(9), gsm_error(9), gsm_cleanup_mux(9), gsm_activate_mux(9), gsm_free_mux(9), gsm_free_muxr(9), gsm_alloc_mux(9), gsmld_output(9), gsmld_write_trigger(9), gsmld_write_task(9), gsmld_attach_gsm(9), gsmld_detach_gsm(9), gsmld_flush_buffer(9), gsmld_close(9), gsmld_open(9), gsmld_write_wakeup(9), gsmld_read(9), gsmld_write(9), gsmld_poll(9), gsm_modem_upd_via_data(9), gsm_modem_upd_via_msc(9), gsm_modem_update(9), gsm_wait_modem_change(9)


Like, that's the whole reading list. Screenshot it, bookmark it, print it out and put it on your wall πŸ™ˆ

And that's the page, bestie πŸ’œ Signing off from ./drivers/tty, dated October 2026 β€” periodt, slay, go send that control frame 🧚πŸ”₯

πŸ“¦ where this page comes from