On 23/09/13 16:45, Christian König wrote:
> All what we could do is to avoid the code dublication for each target.
> For this I would like to arrange the target like this:
>
> r600
> |-dri
> |-vdpau
> |-xorg
> |xvmc
> ...
> radeonsi
> |-dri
> |-vdpau
> |-xorg
> ...
>
I was pondering on the
Am 23.09.2013 16:52, schrieb Marek Olšák:
This is kind of hard to read. I think it would be nicer to:
1) Move the pipe_reference variable from the winsys to the screen.
2) Have the screen create the winsys, instead of just receiving a
pointer to it, so that the winsys doesn't have to be
reference
This is kind of hard to read. I think it would be nicer to:
1) Move the pipe_reference variable from the winsys to the screen.
2) Have the screen create the winsys, instead of just receiving a
pointer to it, so that the winsys doesn't have to be
reference-counted, because the screen is.
Marek
On
From: Christian König
Only create one screen for each winsys instance.
This helps with buffer sharing and interop handling.
Signed-off-by: Christian König
---
src/gallium/drivers/r300/r300_screen.c| 3 +++
src/gallium/drivers/r600/r600_pipe.c | 3 +++
src/gallium/dri
