On 01/27/2017 05:34 AM, Dieter Nützel wrote:
Question more about the first one
[Mesa-dev] [PATCH 1/2] gallium/radeon: query the CPU accessiblesize
of VRAM
Is vram_vis_size > vram_size valid?
After some time I get this on r600/Turks XT/6670/2 GB:
/opt/mesa> setenv R600_DEBUG info
/opt/mes
Question more about the first one
[Mesa-dev] [PATCH 1/2] gallium/radeon: query the CPU accessible size of
VRAM
Is vram_vis_size > vram_size valid?
After some time I get this on r600/Turks XT/6670/2 GB:
/opt/mesa> setenv R600_DEBUG info
/opt/mesa> glxgears
pci_id = 0x6758
family = 45 (AMD TURK
For the series:
Reviewed-by: Marek Olšák
On Jan 25, 2017 5:50 PM, "Nicolai Hähnle" wrote:
Reviewed-by: Nicolai Hähnle
On 25.01.2017 16:56, Samuel Pitoiset wrote:
> This new query returns the current visible usage of VRAM accessed
> by the CPU. It will return 0 on radeon because it's unimpl
Reviewed-by: Nicolai Hähnle
On 25.01.2017 16:56, Samuel Pitoiset wrote:
This new query returns the current visible usage of VRAM accessed
by the CPU. It will return 0 on radeon because it's unimplemented.
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/radeon/r600_query.c |
This new query returns the current visible usage of VRAM accessed
by the CPU. It will return 0 on radeon because it's unimplemented.
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/radeon/r600_query.c | 7 +++
src/gallium/drivers/radeon/r600_query.h | 1 +
src/gall
