pvr_page_ta...ntry_raw_set(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pvr_page_ta...ntry_raw_set(9) πŸ’…

okay so bestie, this is the Kernel API Manual page for pvr_page_ta...ntry_raw_set(9), and it’s literally about writing a valid entry into a raw level 2 page table. tiny function, very specific job, main character energy fr fr πŸŽ€


✨ NAME ✨

pvr_page_table_l2_entry_raw_set β€” write a valid entry into a raw level 2 page table. that’s the whole vibe. πŸ’–


🌸 SYNOPSIS 🌸

void pvr_page_table_l2_entry_raw_set (struct pvr_page_table_l2_entry_raw
*entry , dma_addr_t child_table_dma_addr );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • entry β€” the target raw level 2 page table entry. this is the little spot you’re writing into, bestie ✨
  • child_table_dma_addr β€” the DMA address of the level 1 page table that’s getting associated with entry. yes, it’s a whole page-table situationship πŸ’…

πŸ”₯ DESCRIPTION πŸ”₯

When you call this function, child_table_dma_addr must be a valid DMA address, and it must be a multiple of ROGUE_MMUCTRL_PC_DATA_PD_BASE_ALIGNSIZE. no cap. this is a hard requirement, not a suggestion 🫢

bestie please respect the alignment rule. the manual says β€œmust,” and we do not argue with a β€œmust” in a kernel API page 😭

🌈 SEE ALSO 🌈


that’s the whole page, bestie. it lives under ./drivers/gpu/drm/imagination, dated October 2026, and it’s literally pvr_page_ta...ntry_raw_set(9) β€” iconic, specific, and fully aligned (when you follow the rule) πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from