gsm_dlci_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– gsm_dlci_alloc(9) β€” Kernel API Manual, bestie edition ✨

okay so this is the page for gsm_dlci_alloc(9), straight out of the Kernel API Manual. it's a little function with big main character energy, and we're gonna get into it πŸŽ€


🌸 NAME 🌸

gsm_dlci_alloc β€” allocate a DLCI. that's it, that's the whole vibe ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

struct gsm_dlci * gsm_dlci_alloc (struct gsm_mux *gsm , int addr );

πŸŽ€ ARGUMENTS πŸŽ€

  • gsm β€” the GSM mux. the whole multiplexed situation you're plugging into πŸ‘‘
  • addr β€” the address of the DLCI. literally the address, that's the whole thing πŸ’…

πŸ’… DESCRIPTION πŸ’…

so what does it do? it allocates and installs a new DLCI object into the GSM mux. allocate, install, done. the DLCI gets a whole new life in the mux, slay 🫢

⚠️ FIXME: review locking races β€” i'm just the messenger bestie, this is a real note that's literally in the source. locking races are not cute. do not ignore, fr fr πŸ’€

that's genuinely everything on this page, no filler, no extra lore. short king behavior πŸ‘‘


🌈 SEE ALSO 🌈

there's also the whole kernel file at ./drivers/tty/n_gsm.c, and honestly the friend group here is huge, so buckle up πŸ¦‹

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_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 i said. huge friend group. iykyk πŸ’œ


and that's the page!! mwah πŸ’‹ this little writeup comes from ./drivers/tty, dated October 2026, and it's filed under gsm_dlci_alloc(9) β€” go off, king πŸ‘‘βœ¨

πŸ“¦ where this page comes from