vme_dma_request(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vme_dma_request(9) β€” like, the VME DMA controller request page, bestie ✨

okay so real talk, this one lives in the Kernel API Manual, and it's the page for vme_dma_request(9). it's short, it's sweet, and it's literally the "hey kernel, can I borrow a DMA controller please πŸ₯Ί" call. let's get into it 🌸


✨ NAME ✨

vme_dma_request β€” request a DMA controller. that's it, that's the whole vibe πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

struct vme_resource * vme_dma_request (struct vme_dev *vdev , u32 route );

she takes two things and gives you back a pointer to a struct vme_resource β€” or nothing at all. no cap 😭


πŸ“ ARGUMENTS πŸ“

  • vdev β€” pointer to the VME device struct vme_dev that's been assigned to your driver instance. like, your device. the one you're claiming 🫢
  • route β€” the required src/destination combination. so basically you tell her which two things you want to move data between, and she checks that combo is even a thing πŸ‘‘

πŸ’œ DESCRIPTION πŸ’œ

okay so here's the deal: you call this when you want a VME DMA controller that actually has the capability to perform transfers between the source/destination combination you asked for in route. it's giving "matchmaker but for hardware" πŸ’–

you're not configuring anything yet, you're not moving any bytes yet β€” you're just requesting the controller that can do the combo you want. main character energy, honestly ✨


πŸ”₯ RETURN πŸ”₯

  • pointer to a VME DMA resource on success πŸŽ‰ slay
  • NULL on failure πŸ’€ (and yes, bestie, you must check for the NULL β€” do not just raw-dog that pointer, i'm begging πŸ™ˆ)

🌈 SEE ALSO 🌈

kernel file ./drivers/staging/vme_user/vme.c, plus the whole friend group of VME functions, fr fr:


πŸ’‘ tiny note bestie: don't forget vme_dma_free(9) exists for when you're done with whatever vme_dma_request handed you 🧚 that's just the list being a good friend, i'm not adding anything, promise πŸ’…

and that's the page!! mwah 😘 this one comes out of ./drivers/staging/vme_user, dated October 2026 β€” screenshot it, cite it, cite it in your commit message, idc, go off πŸ‘‘πŸ’–

πŸ“¦ where this page comes from