n_hdlc_send_frames(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… n_hdlc_send_frames β€” the Kernel API Manual (section 9, bestie) 🌸

okay so real talk, we're in Kernel API Manual territory, section 9, and today's main character is n_hdlc_send_frames. she's a function, she's a whole vibe, and she pushes frames out. let's get into it ✨


πŸŽ€ NAME πŸŽ€

n_hdlc_send_frames β€” send frames on the pending send buffer list like it's her job (it literally is) πŸ’…


✨ SYNOPSIS ✨

void n_hdlc_send_frames (struct n_hdlc *n_hdlc , struct tty_struct *tty
);

no return value, she just does the thing. void queen 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • n_hdlc β€” pointer to the ldisc instance data, iykyk 🌈
  • tty β€” pointer to the tty instance data, bestie fr fr 🌸

πŸ”₯ DESCRIPTION πŸ”₯

okay so here's the tea: n_hdlc_send_frames sends frames on the pending send buffer list until the driver does not accept a frame (busy). so basically she keeps going until the driver's like "nope, busy, not today" πŸ’€ and that's the stopping point, no cap.

and when does this function get called? two moments, bestie, both iconic πŸ‘‘

  1. after adding a frame to the send buffer list πŸŽ€
  2. by the tty wakeup callback ⭐

that's the whole flow. she shows up, she sends what she can, the driver says when. periodt. πŸ’œ


πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group, all of them, no one left out 🫢:


and that's the page, bestie! πŸ’– this one lives under ./drivers/tty, it's dated October 2026, and you can find her filed as n_hdlc_send_frames(9) β€” go off, manual page, you ate πŸ”₯πŸ‘‘πŸ’…
πŸ“¦ where this page comes from