https://bugs.freedesktop.org/show_bug.cgi?id=107670
--- Comment #15 from [email protected] ---
(In reply to Michel Dänzer from comment #14)
> (In reply to iive from comment #13)
> > It looks to me like the data is first moved ram->vram using dma, then
> > vram->vram using CPU...
>
> No. u_upload_data is for copying data from normal system memory into GPU
> accessible memory. (You're comparing physical and virtual memory addresses,
> AKA apples and oranges :)
Not really.
It is custom of the linux kernel to repeat the physical addresses as effective
mappings, it simplifies a number of things. Also, this is not system memory
that could be freed and reused in any order at kernel discretion, It is a frame
buffer that is mapped from another device and the relative addressing should be
preserved, as much as possible.
Aka, I do expect that the whole 512MB buffer is mapped at once.
So if one of these addresses is in vram, then the other should be too.
You could probably help me (dis)prove this, by telling me how to obtain the
effective address of the frame-buffer. Xorg.0.log lists only:
[ 114.494] (--) PCI:*(1@0:0:0) 1002:68d8:1458:21d9 rev 0, Mem @
0xe0000000/268435456, 0xfbdc0000/131072, I/O @ 0x0000ce00/256, BIOS @
0x????????/131072
I do understand that u_upload_data() is for coping data from normal system
memory into GPU accessible memory, so coping vram->vram should be some kind of
bug.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
