hvc_iucv_dtr_rts(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… hvc_iucv_dtr_rts(9) β€” the Kernel API Manual, bestie edition

Okay so this page lives in the Kernel API Manual section 9, and it's all about hvc_iucv_dtr_rts β€” the HVC notifier that handles DTR/RTS. Yes, those modem-line thingies. We're going old school but make it kernel. πŸŽ€


✨ SYNOPSIS ✨

void hvc_iucv_dtr_rts (struct hvc_struct *hp , bool active );

That's it. That's the whole vibe. Two args, no return value, zero drama. πŸ’…


🫢 ARGUMENTS 🫢

  • hp β€” a pointer to the HVC device, and like, the type is struct hvc_struct, so you know exactly what kind of creature you're holding. πŸ¦‹
  • active β€” true if you wanna raise the DTR/RTS lines, false if you wanna lower them. Binary queen behavior, honestly. ⭐

🌸 DESCRIPTION 🌸

So this routine's whole job is to notify the HVC back-end to raise or lower the DTR/RTS lines. That's it. That's the assignment. πŸ’–

Now here's the tea: raising DTR/RTS is ignored. Like, completely. Nothing happens. It's giving "seen, but no reply." πŸ™ˆ

But lowering DTR/RTS? That's the main character moment. πŸ‘‘ Lowering them indicates to drop the IUCV connection β€” similar to hanging up the modem. So yeah, it's basically the kernel equivalent of ending the call. 😭


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/tty/hvc/hvc_iucv.c, plus this whole friend group right here:


Full disclosure, bestie: this page is filed under ./drivers/tty/hvc, and the version stamp on it says October 2026. So yeah β€” that's the source, that's the date, that's the whole receipt. 🧚 No cap. πŸ’œ
πŸ“¦ where this page comes from