On Wed, Jun 29, 2011 at 4:12 PM, Thomas Hellstrom wrote:
[snipped]
> diff --git a/src/gallium/state_trackers/vega/vg_manager.c
> b/src/gallium/state_trackers/vega/vg_manager.c
> index eeea686..dec1581 100644
> --- a/src/gallium/state_trackers/vega/vg_manager.c
> +++ b/src/gallium/state_trackers/v
- Original Message -
> On 06/29/2011 10:10 AM, Jose Fonseca wrote:
> > - Original Message -
> >
> >> Note that the state trackers themselves don't use atomic stamps on
> >> frame-buffers. Multiple context rendering to the same drawable
> >> should
> >> be protected by the appl
On 06/29/2011 10:10 AM, Jose Fonseca wrote:
- Original Message -
Note that the state trackers themselves don't use atomic stamps on
frame-buffers. Multiple context rendering to the same drawable should
be protected by the application.
I known that contexts must not be used by
- Original Message -
> Note that the state trackers themselves don't use atomic stamps on
> frame-buffers. Multiple context rendering to the same drawable should
> be protected by the application.
I known that contexts must not be used by two threads simultaneously, but I
don't recall eve
The api and the state tracker manager code as well as the state tracker code
assumed that only a single context could be bound to a drawable. That is not
a valid assumption, since multiple contexts can bind to the same drawable.
Fix this by making it the state tracker's responsibility to update al
