gsm_dlci_set_wait_config(9)
π gsm_dlci_set_wait_config(9) β from the Kernel API Manual, bestie π
Okay so picture this: you're deep in the kernel, you've got a DLCI situation on your hands, and you just need it to chill until the application tells you what's up. That's literally this whole function. No cap, that's it. Let's go β¨
πΈ NAME πΈ
gsm_dlci_set_wait_config β wait for channel configuration
Girl, it does exactly what it says on the tin. It waits. For configuration. For a channel. Iconic behavior honestly.
π¦ SYNOPSIS π¦
void gsm_dlci_set_wait_config (struct gsm_dlci *dlci );
That's the whole vibe. Void return, one pointer, no drama. π«Ά
π ARGUMENTS π
dlciβ theDLCIto configure. This is the main character of the operation, bestie. Hand it over and let it know it's time to get configured.
π DESCRIPTION π
Wait for a DLCI configuration from the application.
That's literally the whole thing. No secret bonus lore, no hidden plot twist β you're just parked here, waiting for the app to send over the configuration for this DLCI. Think of it as the kernel holding the door open like "whenever you're ready, babe π
".
Ngl this one's short but that doesn't make it not important. It's giving "quietly essential supporting character". π
π₯ SEE ALSO π₯
The whole friend group, fr fr. Every single one of these is part of the ./drivers/tty/n_gsm.c cinematic universe β kernel file ./drivers/tty/n_gsm.c:
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_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 the whole squad. Go read them, iykyk. πβ¨
<div align="center">
πΈ that's the page, bestie πΈ
</div>
This lil masterpiece comes from ./drivers/tty and it's dated October 2026 β shoutout to that source and version, mwah ππ Keep slaying out there in the tty layer, and remember: when in doubt, wait for config. 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