hvterm_raw_put_chars(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

hvterm_raw_put_chars β€” bestie, this is the one that sends characters straight to the firmware for a given vterm adapter. no cap. ✨

so like, you're in the kernel Kernel API Manual (section 9, drivers, the whole vibe) and this function is your lil messenger girl handing chars off to firmware. πŸŽ€


🌸 SYNOPSIS 🌸

ssize_t hvterm_raw_put_chars (uint32_t vtermno , const u8 *buf , size_t count );

like, it returns an ssize_t and takes three things. that's the whole fit. πŸ’…


✨ ARGUMENTS ✨

  • vtermno β€” the virtual terminal number. which vterm are we talking to, girlypop? πŸ¦‹
  • buf β€” the characters you're sending. ok but here's the tea: because of the underlying hypercall in hvc_put_chars, this buffer must be at least 16 bytes long, even if you're literally sending fewer chars. not me warning you twice. 16 bytes minimum. periodt. 😭
  • count β€” number of chars to send. the actual amount. the real ones. ⭐
🫢 lowkey important: that 16-byte thing on buf is not a suggestion, it's a requirement. don't come crying to me when your buffer is 4 bytes and the hypercall side-eyes you. πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

  • Kernel file ./drivers/tty/hvc/hvc_vio.c β€” go read it, iykyk πŸ‘‘

🌈 okay that's the whole page, mwah πŸ’œ β€” this icon was living in ./drivers/tty/hvc, dated October 2026, and it answers to the name hvterm_raw_put_chars(9). slay. πŸŽ€πŸ’–

πŸ“¦ where this page comes from