NVIIC(4)

πŸ“¦ in nixpkgs unstable

πŸ’… NVIIC πŸ’…

okay so bestie, this is the manual page for nviic β€” a kernel interfaces manual situation, and honestly? it's giving "niche but essential." let's get into it 🫢


✨ NAME ✨

nviic β€” the NVIDIA nForce2/3/4 SMBus controller driver. yes, that entire string of numbers is part of the name. it's not a typo, it's a family tree 🌳


🌸 SYNOPSIS 🌸

nviic* at pci?
iic* at nviic?

so basically nviic hangs off pci?, and then iic* hangs off nviic?. it's a whole little ecosystem. very "found family" of you, honestly πŸ’–


πŸ¦‹ DESCRIPTION πŸ¦‹

the nviic driver is the supportive bestie for the NVIDIA nForce2/3/4 SMBus host interface β€” and also the MCP51/55/61/65/67/73/77/79/89 ones, which, yes, is a lot of numbers, we love a thorough list πŸ‘‘

it's made to be used with the iic(4) framework. that's the whole vibe. no cap.


πŸŽ€ SEE ALSO πŸŽ€

go read those too, i'm literally begging you πŸ₯Ί they're iconic in their own right.


🌈 HISTORY 🌈

the nviic driver first appeared in OpenBSD 3.9. vintage. lowkey a little retro moment πŸ’Ύβœ¨


🧚 AUTHORS 🧚

the nviic driver was written by David Gwynne <dlg@openbsd.org>. legend behavior, fr fr πŸ’œ


πŸ’€ BUGS πŸ’€

okay so here's the tea, and it's a real one: the driver doesn't support I2C commands with a data buffer size of more than 2 bytes. that's it. that's the limit. two bytes and not a single one more 😭 don't come at me, it's just what the page says.

ngl this is the kind of caveat you find out the hard way, so maybe write it on a sticky note πŸ“

that's the whole page, bestie β€” every flag-worthy detail intact, nothing skipped, nothing invented. mwah πŸ’…

sign-off time πŸŽ€ this one's from the Debian edition of the manual, dated July 16, 2013 β€” old enough to have its own myspace, and yet here we are, still reading it. slay. 🌸

πŸ“¦ where this page comes from
  • nixpkgs unstable: cvs-export
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms