vme_master_write(9)

💖 vme_master_write(9) 💖

okay so bestie, welcome to the Kernel API Manual page for vme_master_write(9) — manual name folded in right here, no boring header-line copy-paste energy. This is the function where you write data out to VME space from a buffer, and it's genuinely giving "I know my VME master window" vibes. 🌸

✨ NAME ✨

vme_master_write — Write data out to VME space from a buffer. periodt. That's the name and the whole assignment. 💅

🦋 SYNOPSIS 🦋

       ssize_t vme_master_write (struct vme_resource *resource , void *buf ,
       size_t count , loff_t offset );

🎀 ARGUMENTS 🎀

• resource — Pointer to VME master resource. lowkey your VIP pass to the VME master situation. ✨
• buf — Pointer to buffer holding data to transfer. this is where the data is coming from, bestie. 🫶
• count — Number of bytes to transfer. yes, the amount — exact number of bytes, no vibes-based guessing. 💖
• offset — Offset into VME master window at which to start transfer. where in the window we're starting, fr fr. 🌈

💫 DESCRIPTION 💫

Okay so what it does: it performs a write of count bytes of data from buf to the location on the VME bus which maps into the VME master window at offset. That's it. That's the assignment. It's giving "move those bytes into the right window spot" and honestly? iconic. 🔥

👑 RETURN 👑

• Number of bytes written — the success glow-up number. ✨
• -EINVAL — if resource is not a VME master resource or write operation is not supported. not the right resource? not supported? boom, -EINVAL. 💀
• -EFAULT — returned if invalid offset is provided. invalid offset = -EFAULT, no cap. 🙈
• Hardware specific errors may also be returned. so yeah, hardware can also throw its own errors — keep that in mind. 🫶

🌈 SEE ALSO 🌈

Kernel file ./drivers/staging/vme_user/vme.c — say hi to the source file, bestie. Then the whole friend group:

• 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_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)

sign-off bestie: source/version ./drivers/staging/vme_user, dated October 2026, page vme_master_write(9) — slay your VME writes 💖✨🎀