UVSCOM(4)

πŸ“¦
version 15.1 Β· 3 versions
, in freebsd 14.5, freebsd 15.1, nixpkgs unstable

πŸ’… UVSCOM(4) β€” ok so this is the uvscom manual page, section 4 of the kernel interfaces manual πŸŽ€

Bestie. Gather round. We're talking about the driver for USB support for SUNTAC Slipper U VS-10U serial adapters, and honestly? It's giving niche-but-iconic. ✨


🌸 NAME 🌸

uvscom β€” the USB support driver for SUNTAC Slipper U VS-10U serial adapters. That's the whole vibe. No cap.


✨ SYNOPSIS ✨

So you wanna compile this driver into the kernel? Respect. Drop these lines into your kernel configuration file, exactly like this, no notes:

device usb
device ucom
device uvscom

Or β€” lowkey the easier route β€” you can load the driver as a module at boot time instead. For that, go put this line in loader.conf(5):

uvscom_load="YES"

Slay. That's it. 🫢


πŸ”₯ HARDWARE πŸ”₯

The uvscom driver supports these adapters, and I'm listing every single one because we don't do omissions here, periodt:

  • DDI Pocket Air H" C@rd
  • DDI Pocket Air H" C@rd 64
  • NTT P-in
  • NTT P-in m@ster

(yes, the C@rd spelling is real, that's the actual product name, don't come for me πŸ’€)


πŸ’– DESCRIPTION πŸ’–

Okay so what does uvscom actually do? It provides support for the SUNTAC Slipper U VS-10U chip. And Slipper U β€” main character energy, honestly β€” is a PC Card to USB converter for data communication card adapters. Like it takes your data communication card adapter and makes it a USB thing. Iconic little middleman. πŸ¦‹

The device is accessed through the ucom(4) driver, which is what makes it behave like a tty(4). So basically: it walks in wearing ucom's clothes and pretends to be a terminal. And it works. πŸŽ€


πŸŽ€ FILES πŸŽ€

Here's your file map, bestie, learn it, love it:

  • /dev/ttyU* β€” for callin ports
  • /dev/ttyU*.init
  • /dev/ttyU*.lock β€” the corresponding callin initial-state and lock-state devices

and then the callout side:

  • /dev/cuaU* β€” for callout ports
  • /dev/cuaU*.init
  • /dev/cuaU*.lock β€” the corresponding callout initial-state and lock-state devices

✨ callin vs callout, init vs lock, know the difference, iykyk ✨


πŸ‘‘ SEE ALSO πŸ‘‘

Go read these next, in this exact order if you're feeling tidy:


🌈 HISTORY 🌈

The uvscom driver first appeared in FreeBSD and later in NetBSD 1.6. And this manual page was adopted from NetBSD by Tom Rhodes <trhodes@FreeBSD.org> in April 2002. Shoutout Tom. 🫢


⭐ quick vibe check: everything above is straight from the page β€” nothing invented, nothing skipped, no guessing at behaviour. That's the rule. πŸ’…

and that's the whole manpage, bestie, you ate that πŸ“ β€” this page is from Debian, dated April 26, 2017, and it covers UVSCOM(4) in full. mwah πŸ’‹

πŸ“¦ where this page comes from