vme_master_get(9)

💖 vme_master_get(9) — like, the whole Kernel API Manual page, bestie 💖

okay so this is vme_master_get(9), straight out of the Kernel API Manual (section 9, we're fancy like that ✨). It's the little function that goes "hey, what's the config on this VME master window?" and honestly? we stan a read-only getter that minds its own business 🫶

---

✨ NAME ✨

vme_master_get — Retrieve VME master window configuration.

that's it. that's the job. it gets. it retrieves. it slays 💅

---

🦋 SYNOPSIS 🦋

int vme_master_get (struct vme_resource *resource , int *enabled ,
unsigned long long *vme_base , unsigned long long *size , u32 *aspace ,
u32 *cycle , u32 *dwidth );

look at all those pointers. seven of them. it's giving "I have a lot of things to tell you and I'm gonna tell you through your own variables" 😭✨

---

🎀 ARGUMENTS 🎀

• resource — Pointer to VME master resource. this is the main character, everything else is just vibes orbiting it 👑
• enabled — Pointer to variable for storing state. like, is the window even on or not
• vme_base — Pointer to variable for storing window base address. where the window starts, location-wise
• size — Pointer to variable for storing window size. how much room we're working with, no cap
• aspace — Pointer to variable for storing VME address space. which address space, exactly
• cycle — Pointer to variable for storing VME data transfer cycle type. the type of cycle, iykyk
• dwidth — Pointer to variable for storing VME data transfer width. how wide the data transfer is going, literally

every single one of these is a pointer, so like, you're handing the function places to write into. it's not returning anything to you directly, it's filling your variables in. teamwork fr fr 💜

---

🌸 DESCRIPTION 🌸

Return configuration for provided VME master window.

short. sweet. zero notes. you give it the window, it gives you the config. iconic behavior, honestly 🧚✨

---

🔥 RETURN 🔥

• Zero on success 🎉 — we love a clean exit
• -EINVAL if the operation is not supported on this device, or if an invalid resource has been provided 💀

so if you're getting -EINVAL, you either used a device that doesn't do this, or you fed it a bad resource. either way, that's a vibe check that did not pass 🙈

---

🌈 SEE ALSO 🌈

okay bestie, buckle up, because this list is LONG and every single one of these matters 🫶

Source file: Kernel file ./drivers/staging/vme_user/vme.c

Then, in order, all the friends:

vme_alloc_consistent(9), vme_free_consistent(9), vme_get_size(9), vme_slave_request(9), vme_slave_set(9), vme_slave_get(9), vme_slave_free(9), vme_master_request(9), vme_master_set(9), vme_master_read(9), vme_master_write(9), vme_master_rmw(9), vme_master_mmap_prepare(9), vme_master_free(9), vme_dma_request(9), vme_new_dma_list(9), vme_dma_pattern_attribute(9), vme_dma_pci_attribute(9), vme_dma_vme_attribute(9), vme_dma_free_attribute(9), vme_dma_list_add(9), vme_dma_list_exec(9), vme_dma_list_free(9), vme_dma_free(9), vme_irq_request(9), vme_irq_free(9), vme_irq_generate(9), vme_lm_request(9), vme_lm_count(9), vme_lm_set(9), vme_lm_get(9), vme_lm_attach(9), vme_lm_detach(9), vme_lm_free(9), vme_slot_num(9), vme_bus_num(9), vme_register_driver(9), vme_unregister_driver(9)

like I said. LONG. but that's literally every one of them, don't come for me 😤💖

---

sign-off era 🎀✨

this page lives under ./drivers/staging/vme_user and it's dated October 2026 — yes, October 2026, she's from the future and she's still explaining VME master windows 💫

now go read your config, bestie. vme_master_get believes in you 💜🦋🌸