gsm_control_command(9)
π« 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 thatdatawe'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 π«Ά:
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_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_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)
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
- 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