gsm_alloc_mux(9)
π gsm_alloc_mux(9) β straight from the Kernel API Manual, bestie β¨
okay so picture this: you're deep in the kernel, the manual is literally called Kernel API Manual, and the page you opened is gsm_alloc_mux(9). she's short, she's sweet, she's the first domino in the whole mux saga π
πΈ NAME
gsm_alloc_mux β allocate a mux π
β¨ SYNOPSIS
struct gsm_mux * gsm_alloc_mux (void );
π«Ά ARGUMENTS
voidβ no arguments, bestie. not a single one. she takes nothing and gives you a whole mux π
π DESCRIPTION
Creates a new mux ready for activation β¨
that's it, that's the whole lore. you call her, she hands you a fresh mux, and it's sitting there all ready-to-be-activated like a new character waiting for her entrance. no cap, this is the main character energy moment of the whole GSM mux pipeline π
ngl this page is teeny tiny β but that just means the real chaos lives over in SEE ALSO. buckle up π¦
π₯ SEE ALSO
okay so THIS is the group chat. like, the entire extended friend group of n_gsm. all of these live in the kernel file ./drivers/tty/n_gsm.c, and honestly? she's popular. 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_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_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)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 where does all this live? the directory ./drivers/tty, periodt π
π reminder for the girlies: gsm_alloc_mux gives you a mux ready for activation β that's it, that's the whole claim. don't be out here assuming she activates it for you π
π§ and that's the page!! sourced from the ./drivers/tty corner of the tree, dated October 2026, brought to you by the Kernel API Manual β mwah, see u in the next manpage bestie ππβ¨
π¦ 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