ISV(4)
π ISV(4) β the IDEC Supervision/16 image capture board page, bestie edition π
okay so this is the manual page for isv, section 4 (kernel interfaces manual, iykyk) β and honestly? it's giving "niche 90s video capture hardware that only a true Unix girlie would stan." let's get into it β¨
πΈ NAME πΈ
isv β the IDEC Supervision/16 image capture board. that's it, that's the whole vibe. a whole board. for capturing images. iconic.
π¦ SYNOPSIS π¦
isv0 at isa? port 0x2f0
isv0 at isa? port 0x2e0
isv0 at isa? port 0x3f0
isv0 at isa? port 0x3e0
so you've got four port options and you literally just pick one, no cap. isa? means "wherever the ISA bus is at, bestie." π«Ά
β¨ DESCRIPTION β¨
okay so isv is a driver for the IDEC Supervision/16, and this thing is an image capture board that plugs into a 16-bit ISA bus. vintage. retro. a little bit slay.
here's the tea on what it actually does: the IDEC Supervision/16 digitizes an NTSC television signal, and it stores a 512 x 480-pixel, 8-bit grayscale image in its 256kB dynamic RAM array β and it does that every 1/30th of a second. π every single frame, 30 times a second, no big deal.
and how does the host get those frames out? the host reads frames from the DRAM using 122881 16-bit I/O reads. yes, that is a very specific number. no, we're not rounding it. 122881. write it down. π
ngl, reading frames from the Supervision/16 is quite slow: after the host reads a 16-bit word from the DRAM, the Supervision/16 state machine takes approximately 0.5 microseconds to get ready for the next read. the way that state machine needs a little breather between reads π
theoretically, a frame rate of approximately 10 frames per second is possible. theoretically. in theory. hypothetically. π
but isv actually achieves a frame rate of approximately 6 frames per second. so likeβ¦ it tried its best and we love it anyway. π
π SEE ALSO π
- Programming the Supervision/16 Image Capture Board, IDEC, circa 1991. β yes, circa 1991, the ancient texts, the sacred scrolls, go read them π
π HISTORY π
the isv device first appeared in NetBSD 5.0. a debut. a moment. π
π AUTHORS π
the isv driver was written by David Young <dyoung@NetBSD.org>. we stan a driver author with a NetBSD email address fr fr π
π BUGS π
- Synchronizing with the hardware and reading frames from it is very CPU-intensive. like, your CPU is gonna feel it. it's working overtime. π«
isvwill not detect the capture board if it is not attached to an active video source. no signal, no detection, that's the rule. to force NetBSD to detect the capture board at any time, re-scan the ISA bus using, e.g.,drvctl -r isa0. boom, problem solved, you're welcome π
real talk though: that no-active-video-source thing will absolutely trip you up if you forget, so likeβ¦ plug in a video source first, bestie. i'm begging π
aaaand that's the whole page! this beauty came from the Debian crew, dated April 1, 2008 β yes, April Fools' Day, and no, i don't think that's a coincidence π happy capturing, go read your drvctl page next, mwah πβ¨π¦
π¦ where this page comes from
- nixpkgs unstable: netbsd-source 11.0
- Copyright (c) 2008 The NetBSD Foundation, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms