vme_dma_list_exec(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay so welcome to the Kernel API Manual, bestie β€” today's main character is vme_dma_list_exec, and she's literally here to queue a VME DMA list for execution. periodt. ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

int vme_dma_list_exec (struct vme_dma_list *list );

πŸŽ€ ARGUMENTS πŸŽ€

  • list β€” a pointer to the VME list, iykyk 🫢

πŸ’– DESCRIPTION πŸ’–

So here's the tea: you hand over the VME DMA list you've been building, and this call queues the provided VME DMA list for execution. The call will return once the list has been executed β€” like, it's not gonna ghost you mid-operation, it comes back when the list is done. no cap. πŸ’…

🌸 RETURN 🌸

  • 0 β€” success, slay ✨
  • -EINVAL β€” if the operation is not supported on this device, awkward πŸ™ˆ
  • hardware specific errors β€” also possible, because hardware loves to be dramatic 😭

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/staging/vme_user/vme.c β€” and the whole squad is here: 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_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). πŸ«ΆπŸ’–


mwah πŸ’‹ this page is served fresh from ./drivers/staging/vme_user, dated October 2026, and it's literally vme_dma_list_exec(9) β€” catch you in the next manpage, bestie! πŸ«ΆπŸ’–

πŸ“¦ where this page comes from