gsm_response(9)
π gsm_response(9) π
okay so this is a page from the Kernel API Manual β yes, the Kernel API Manual, we're being fancy today β and it's all about gsm_response, bestie. it's short, it's sweet, it sends a control response. let's get into it π«Ά
β¨ SYNOPSIS β¨
void gsm_response (struct gsm_mux *gsm , int addr , int control );
that's the whole signature. returns nothing (void), takes three things. iconic, minimal, no notes π
π ARGUMENTS π
gsmβ our GSM mux. our mux. ours. π₯° (it's astruct gsm_mux *)addrβ the address for the control frame π¬controlβ the control byte, and yes it includes the PF bit β don't forget the PF bit, i'm literally begging π
πΈ DESCRIPTION πΈ
so what does it actually do? it formats up a link level response frame and then transmits it. that's it. that's the whole job β¨
fr fr that's the entire description in the original β format it, transmit it, done. no cap, some functions are just built different (and some are just built simple) π¦
π SEE ALSO π
the kernel file lives at ./drivers/tty/n_gsm.c β go read it, it's giving main character energy π
and here's the whole squad, every single one of them, in order, because we do not leave anyone out of the group chat π:
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_send(9), gsm_dlci_clear_queues(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 a lot of friends. obsessed π
aaaand that's the page!! mwah π this little cutie comes to you from ./drivers/tty, dated October 2026, under the Kernel API Manual banner β catch you in the next man page, bestie, slay π§ββοΈβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms