ppc440spe_ad...p_dma_memcpy(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

ppc440spe_adma_prep_dma_memcpy — bestie, this one's entire personality is preparing a CDB for a MEMCPY operation. That's it, that's the job. It's a Kernel API Manual girly (yes, we're in the Kernel API Manual, welcome 💖), and it does exactly one little thing: get that command descriptor block ready so the memcpy can happen. Slay.

✨ SYNOPSIS ✨

struct dma_async_tx_descriptor * ppc440spe_adma_prep_dma_memcpy (struct
dma_chan *chan , dma_addr_t dma_dest , dma_addr_t dma_src , size_t len ,
unsigned long flags );

Like, look at her. Five whole parameters. Iconic signature, no notes. 🎀

🫶 ARGUMENTS 🫶

Okay so here's the tea, and I need you to sit down for this one: the documentation for every single argument is literally -- undescribed --. Not me hyping up five mystery men. 😭 So here they are, in order, with the exact amount of lore the page gives us (which is zero):

  • chan — -- undescribed -- 🫥
  • dma_dest — -- undescribed -- 🫥
  • dma_src — -- undescribed -- 🫥
  • len — -- undescribed -- 🫥
  • flags — -- undescribed -- 🫥

That's the whole vibe check. The struct dma_chan * is a channel, the dma_addr_ts are addresses, size_t len is a length and unsigned long flags is flags — that's just the types talking, fr fr, the manual itself is giving silent main character energy. 💀 We respect the mystery.

👑 SEE ALSO 👑

The Kernel file is ./drivers/dma/ppc4xx/adma.c — that's where all the lore lives, bestie. And then there's the family. The whole entire family. This function has, like, so many siblings and I'm listing every single one because nobody gets left behind at this party 🌈:

And that's the page, bestie. It came to us from ./drivers/dma/ppc4xx, dated October 2026, and honestly? A whole era. Go prep that CDB. You got this. 💜🦋

📦 where this page comes from