vme_dma_pci_attribute(9)

📦 version 7.3.1, in nixpkgs unstable

💅 vme_dma_pci_attribute — the one where you make a "PCI" type VME DMA list attribute

ok so picture this: it's the vme_dma_pci_attribute(9) page in the Kernel API Manual, and it's literally the shortest little guy ever. tiny page, huge vibes. let's get into it 🫶

✨ NAME ✨

vme_dma_pci_attribute — Create "PCI" type VME DMA list attribute.

like, that's it, that's the whole name section. icon behavior honestly.

🌸 SYNOPSIS 🌸

struct vme_dma_attr * vme_dma_pci_attribute (dma_addr_t address );

bestie look at that signature. it returns a struct vme_dma_attr * and it takes exactly one (1) argument. no more, no less. we love a low-maintenance function 💖

🎀 ARGUMENTS 🎀

  • address — the PCI base address for the DMA transfer. that's the spot on PCI you're pointing at, bestie. no cap, that's the whole thing.

🦋 DESCRIPTION 🦋

okay so what does it actually do? it creates a VME DMA list attribute that points to a location on PCI, so DMA transfers have somewhere to go. it's giving "setting up the destination" energy. honestly iconic.

⚠️ and here's the part where you gotta listen: it is the responsibility of the user to free used attributes using vme_dma_free_attribute. not the function's job. yours. so don't just walk away from it, okay? that's a leak and leaks are not slay 💀

🔥 RETURN 🔥

  • returns a pointer to the VME DMA attribute 🌟
  • returns NULL on failure 😭

that's it. two outcomes. plot twist potential is lowkey high.

👑 SEE ALSO 👑

first off, the kernel file itself lives at ./drivers/staging/vme_user/vme.c — go say hi 🧚

and then, the whole friend group of VME functions, all in section 9, all present and accounted for:

that's thirty-eight entries, and yes i counted, and yes you should go read them, iykyk 📚✨

and that's the whole page, bestie 🎀 this lil rewrite came straight out of the ./drivers/staging/vme_user corner of the kernel, dated October 2026 — mwah, periodt 💅✨

📦 where this page comes from