vme_slot_num(9)

💅 vme_slot_num(9) — Kernel API Manual 💅

okay so bestie, this is the vme_slot_num(9) page from the Kernel API Manual, and it’s literally the “which slot is this VME device in?” girlie ✨. no cap.

---

🌸 NAME 🌸

vme_slot_num — retrieve the slot ID 💖

---

✨ SYNOPSIS ✨

int vme_slot_num (struct vme_dev *vdev );

---

🎀 ARGUMENTS 🎀

• vdev — pointer to the VME device struct vme_dev that’s assigned to the driver instance 🫶

---

💫 DESCRIPTION 💫

okay so you hand over a VME device, and vme_slot_num() retrieves the slot ID associated with that provided VME device. that’s the whole vibe, bestie 💅

---

🫶 RETURN 🫶

on success you get the slot ID ✨. if the VME bridge cannot be determined, or if the function is not supported, you get -EINVAL 😭. hardware specific errors may also be returned, so don’t act surprised if something hardware-y shows up 👀.

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/staging/vme_user/vme.c is the source bestie, and the whole VME friend group is:

• 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_get(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_bus_num(9)
• vme_register_driver(9)
• vme_unregister_driver(9)

---

xoxo, your ./drivers/staging/vme_user source bestie, from the Kernel API Manual, dated October 2026, vme_slot_num(9) edition 💖