On 12.07.2013 16:19, Jose Fonseca wrote:
I admit I haven't fully understood what's being proposed yet. But just a few
quick words.
I always wanted to have a "present" method that ensures that the contents of a
resource is made visible to whatever the consumer is (full-screen flip, blit to prim
I admit I haven't fully understood what's being proposed yet. But just a few
quick words.
I always wanted to have a "present" method that ensures that the contents of a
resource is made visible to whatever the consumer is (full-screen flip, blit to
primary surface, a compositor, etc.). We have
On Fri, Jul 12, 2013 at 8:31 AM, Marek Olšák wrote:
> Let's ignore the function name for now, that's easy to change and I am
> open to suggestions. flush_window_resource, flush_shared_resource, and
> sync_shared_resource are possible candidates as well as
> gonna_put_this_resource_on_the_screen_ri
Let's ignore the function name for now, that's easy to change and I am
open to suggestions. flush_window_resource, flush_shared_resource, and
sync_shared_resource are possible candidates as well as
gonna_put_this_resource_on_the_screen_right_away. :) The idea is to
expose a function which will ensu
Am 11.07.2013 20:15, schrieb Marek Olšák:
> Hi Roland,
>
> The fast color clear on Radeon doesn't touch the memory of the texture
> resource. Instead, it changes some GPU meta data that say the resource
> is cleared (the location of the meta data is stored in pipe_resource).
> This works fine as l
On 11.07.2013 20:15, Marek Olšák wrote:
> Hi Roland,
>
> The fast color clear on Radeon doesn't touch the memory of the texture
> resource. Instead, it changes some GPU meta data that say the resource
> is cleared (the location of the meta data is stored in pipe_resource).
> This works fine as long
Hi Roland,
The fast color clear on Radeon doesn't touch the memory of the texture
resource. Instead, it changes some GPU meta data that say the resource
is cleared (the location of the meta data is stored in pipe_resource).
This works fine as long as the gallium pipe_resource structure is used
for
I don't quite understand what this should do, at first sight it looks
like a ugly hack (which should really not be part of gallium interface)
to make fast color clearing work better with window framebuffers.
Seems to go against the idea of resources (which are immutable, well not
the contents but t
This interface is used to expand fast-cleared window system
colorbuffers.
---
src/gallium/include/pipe/p_context.h | 8
src/gallium/state_trackers/dri/common/dri_drawable.c | 4
src/gallium/state_trackers/dri/drm/dri2.c| 8 ++--
3 files changed, 18 ins
