PCI_VDEVICE(9)

📦 version 7.3.1, in nixpkgs unstable

💅 PCI_VDEVICE(9) — the Kernel API Manual, bestie edition 🎀

okay so we're diving into PCI_VDEVICE(9) today, from the Kernel API Manual, and honestly? it's a little icon. let's get into it ✨

🌸 NAME 🌸

PCI_VDEVICE — a macro used to describe a specific PCI device in short form 🫶

like, short form. it's giving "don't do too much." main character energy but make it concise 💅

⭐ SYNOPSIS ⭐

PCI_VDEVICE (vend , dev );

that's it. that's the whole vibe. two args, no drama 🌈

🦋 ARGUMENTS 🦋

  • vend — the vendor name 🏷️ (yes bestie, the name, not a number)
  • dev — the 16 bit PCI Device ID 🔢 (sixteen bits of pure identity, no cap)

💖 DESCRIPTION 💖

so the way that this macro WORKS: it's used to create a struct pci_device_id that matches one specific PCI device. periodt. 🎯

and listen — the subvendor and subdevice fields get set to PCI_ANY_ID. so it'll match any subvendor and any subdevice, iykyk. 🤝

the cute part? the macro allows the next field to follow as the device private data. so you get your private data slot handed to you right after, no extra steps. slay 💅

ngl this is the kind of macro that looks tiny and then does exactly three things. respect. 👑

🔥 SEE ALSO 🔥

the whole group chat, fr fr — go read the kernel file ./include/linux/pci.h and then these besties:

that's thirty-two entries bestie, I counted, and I'm obsessed with every single one 🍓

💀 real talk though: it's vend and dev, in that order, and dev is a 16 bit PCI Device ID. don't come for me if you swap them, that's on you 🙈

and that's the page! signing off from ./include/linux, October 2026, in the one and only PCI_VDEVICE(9) era 🧚‍♀️💜✨

📦 where this page comes from