vme_slave_request(9)

📦 version 7.3.1, in nixpkgs unstable

✨ vme_slave_request(9) ✨

okay bestie, welcome to the Kernel API Manual entry for vme_slave_request — yes it's a kernel function, yes it's from ./drivers/staging/vme_user, and yes we're gonna get through it together 💅

🌸 NAME 🌸

vme_slave_request — request a VME slave window resource. that's it, that's the whole vibe 🎀

🦋 SYNOPSIS 🦋

struct vme_resource * vme_slave_request (struct vme_dev *vdev , u32
address , u32 cycle );

literally just hand it a device, an address space, and a cycle type, and it'll try to hook you up 🫶

💖 ARGUMENTS 💖

  • vdev — pointer to the VME device struct vme_dev that's assigned to your driver instance. like, which device are we even talking about, y'know? 👑
  • address — the required VME address space. which little corner of the map you're asking for 🗺️
  • cycle — the required VME data transfer cycle type. the how of the transfer, not just the where ⭐

🔥 DESCRIPTION 🔥

so what this does is: it requests use of a VME window resource — and not just any window, one that's actually capable of being set for the address space you asked for and the data transfer cycle type you asked for. it's giving "matching service but for kernel resources" 😭✨

no cap, that's the whole function. it goes and finds you a window that fits your requirements. periodt 💜

🌈 RETURN 🌈

  • pointer to the VME resource on success 🎉
  • NULL on failure 💀
fr fr check for that NULL, bestie. don't be out here dereferencing a failed request, that's not the main character energy we want 🙈

🧚 SEE ALSO 🧚

the kernel file lives at ./drivers/staging/vme_user/vme.c — and honestly the whole friend group is here, so let me introduce everyone 🌸:

and that's the whole page, bestie!! 💅✨

cute little sign-off before you go: this one's from ./drivers/staging/vme_user, dated October 2026, and it's the vme_slave_request(9) page — go request those windows responsibly, ily 🫶🎀

📦 where this page comes from