vidtv_memcpy(9)

💅 vidtv_memcpy — the Kernel API Manual, bestie edition 🎀

okay so real talk, this page lives in the Kernel API Manual and it's about vidtv_memcpy(9) — the little wrapper that keeps your MPEG-TS generator from yeeting itself straight past the end of the output buffer 😭 no cap, it's a whole safety net.

---

✨ NAME ✨

vidtv_memcpy — a wrapper routine to be used by the MPEG-TS generator, so that it does not go past the output buffer 🫶 literally its whole job.

---

🌸 SYNOPSIS 🌸

u32 vidtv_memcpy (void *to , size_t to_offset , size_t to_size , const
void *from , size_t len );

---

🦋 ARGUMENTS 🦋

• to — the starting element where an MPEG-TS packet is gonna get copied to 💖
• to_offset — the starting position of the to buffer that's getting filled
• to_size — the size of the to buffer, aka the vibe check we do before writing anything
• from — the starting element of the buffer being copied
• len — how many elements get copied from the from buffer into the to+to_offset buffer, fr fr

---

💀 NOTE 💀

Real digital TV demod drivers should not have memcpy wrappers. Like, that's not a thing they should be doing 🙈 We use it here because emulating MPEG-TS generation at kernelspace requires some extra care — it's giving "trust me, we have reasons" and those reasons are real ✨

---

🔥 RETURN 🔥

Returns the number of bytes written 👑 (a u32, in case you were wondering).

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/media/test-drivers/vidtv/vidtv_common.c
• vidtv_memset(9) — her sister function, go say hi 🧚

---

okay so that's the whole page, ate and left no crumbs 💅 this was vidtv_memcpy(9) from the Kernel API Manual, sourced from ./drivers/media/test-drivers/v... and dated October 2026 — see you in the next buffer, bestie, stay within bounds 💜🦋🍓