_pci_add_cap_save_buffer(9)

📦 version 7.3.1, in nixpkgs unstable

✨ _pci_add_cap_save_buffer(9) ✨

okay bestie, so this one lives in the Kernel API Manual (yes, the kernel has lore and yes it's giving ancient scrolls) and it's about grabbing memory so your PCI device's capability registers have somewhere cute to live 💅

🌸 NAME 🌸

_pci_add_cap_save_buffer — allocate buffer for saving given capability registers 🎀

like literally, you're setting aside a lil spot in memory so the capability registers can be saved. that's the whole vibe. no cap.

🌈 SYNOPSIS 🌈

int _pci_add_cap_save_buffer (struct pci_dev *dev , u16 cap , bool extended , unsigned int size );

it returns an int, bestie. take that however you want 😌

💖 ARGUMENTS 💖

  • dev — the PCI device 🫶 (the main character, obviously)
  • cap — the capability to allocate the buffer for ✨ (you gotta tell it which one)
  • extended — Standard or Extended capability ID 🦋 (this lil flag decides which flavor you're speaking)
  • size — requested size of the buffer 🎀 (how much room your girl gets)

👑 SEE ALSO 👑

💀 okay so this list is long long. like, unhinged amounts of siblings. but every single one is here, fr fr — nothing skipped, nothing merged, we respect the whole extended family.

first up, the source file these beauties live in: Kernel file ./drivers/pci/pci.c 🌟

🫶 that's the whole list, i checked twice, we did not lose a single (9). obsessed with our consistency honestly.

and that's the page!! this manual came out of ./drivers/pci and it's dated October 2026 — so yeah, she's from the future, main character energy fr fr 💜✨ mwah, go allocate those buffers bestie 🎀

📦 where this page comes from