gsm_dlci_config(9)
okay so welcome to gsm_dlci_config(9), straight out of the Kernel API Manual, and she is here to configure a DLCI from configuration. bestie, the name is literally the plot π
β¨
π NAME π
gsm_dlci_config β configure DLCI from configuration. that's it, that's the tweet; she configures a DLCI and we love a self-explanatory icon π«Ά
β¨ SYNOPSIS β¨
int gsm_dlci_config (struct gsm_dlci *dlci , struct gsm_dlci_config *dc , int open );
the whole signature, in all its glory β no cap, copy it exactly π
π ARGUMENTS π
dlciβ DLCI to configure. the main character getting the config glow-up πdcβ DLCI configuration. yes, the configuration itself, obviously πopenβ open DLCI after configuration? the question mark is part of the assignment, fr fr π
π¦ SEE ALSO π¦
Kernel file: ./drivers/tty/n_gsm.c β that's home base, go say hi π‘
and the extended fam is genuinely 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_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 π«Ά the source/version line says ./drivers/tty, the date is October 2026, and the manual page name is still gsm_dlci_config(9) β iconic from top to bottom, periodt πβ¨
π¦ 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