vme_dma_vme_attribute(9)
π vme_dma_vme_attribute β the Kernel API Manual moment
okay so bestie, you're looking at the manual page for vme_dma_vme_attribute, straight out of the Kernel API Manual. yes, that's the whole title, we're not skipping it, it's iconic. β¨
πΈ NAME
vme_dma_vme_attribute β Create "VME" type VME DMA list attribute. that's it, that's the job, and it does it fabulously π
π SYNOPSIS
struct vme_dma_attr * vme_dma_vme_attribute (unsigned long long address
, u32 aspace , u32 cycle , u32 dwidth );
look at that signature. gorgeous. no notes. copy it exactly, bestie, character for character, do not freestyle it π«Ά
β ARGUMENTS
addressβ VME base address for DMA transfer. the starting point of the whole vibe, lowkey where the data party begins.aspaceβ VME address space to use for DMA transfer. which address space we're living in, main character energy only.cycleβ VME bus cycle to use for DMA transfer. the bus cycle, fr fr, it matters.dwidthβ VME data width to use for DMA transfer. how wide the data is being. slay.
π¦ DESCRIPTION
Create a VME DMA list attribute pointing to a location on the VME bus, for DMA transfers. that's literally the whole thing: you're making an attribute that says "hey, this is the spot on the VME bus" and DMA goes brrr there.
highkey important though: it is the responsibility of the user to free used attributes using vme_dma_free_attribute. not the kernel's problem, not the compiler's problem, yours. don't leave them lying around like last week's iced coffee π
π₯ RETURN
Pointer to VME DMA attribute, NULL on failure. so if you get NULL back, that's the universe telling you it did not work. check it, bestie, always check it π
π SEE ALSO
Kernel file ./drivers/staging/vme_user/vme.c β and 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_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_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)
ok and a little sign-off moment π this one lives in./drivers/staging/vme_user, dated October 2026, and it's filed undervme_dma_vme_attribute(9)β that's the source, the version vibe and the date, all present and accounted for, no cap. bye bestie, go free your attributes πππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms