On Wed, Mar 11, 2015 at 09:10:01AM -0700, Ian Romanick wrote:
> On 03/06/2015 06:30 AM, Daniel Vetter wrote:
> > On Thu, Mar 05, 2015 at 02:38:44PM -0800, Ian Romanick wrote:
> >> On 03/04/2015 10:28 AM, Chad Versace wrote:
> >>> That text does not appear in the GL spec. When I read the manpage
>
On 03/06/2015 06:30 AM, Daniel Vetter wrote:
> On Thu, Mar 05, 2015 at 02:38:44PM -0800, Ian Romanick wrote:
>> On 03/04/2015 10:28 AM, Chad Versace wrote:
>>> That text does not appear in the GL spec. When I read the manpage alongside
>>> the GL spec, to get a more complete context, I think the ma
On Thu, Mar 05, 2015 at 02:38:44PM -0800, Ian Romanick wrote:
> On 03/04/2015 10:28 AM, Chad Versace wrote:
> > That text does not appear in the GL spec. When I read the manpage alongside
> > the GL spec, to get a more complete context, I think the manpage contains
> > that phrase simply to contras
On Thu, Mar 05, 2015 at 02:38:44PM -0800, Ian Romanick wrote:
> glFlush was invented to support indirect rendering (especially to the
> front buffer): it flushes the buffer in libGL to the xserver. If
> you're making any other assumptions about what it does or does not do...
> continue at your ow
On 03/04/2015 10:28 AM, Chad Versace wrote:
> On 03/04/2015 09:52 AM, Chris Wilson wrote:
>> On Wed, Mar 04, 2015 at 09:41:56AM -0800, Chad Versace wrote:
>>> On 02/26/2015 05:24 AM, Chris Wilson wrote:
When rendering to an fbo, even though it may be acting as a winsys
frontbuffer or just
On Wed, Mar 04, 2015 at 10:28:16AM -0800, Chad Versace wrote:
> On 03/04/2015 09:52 AM, Chris Wilson wrote:
> > The manpage for glFlush says
> >
> > "glFlush can return at any time. It does not wait until the execution of
> > *all*
> > previously issued GL commands is complete."
> >
> > Emphasi
On 03/04/2015 09:52 AM, Chris Wilson wrote:
> On Wed, Mar 04, 2015 at 09:41:56AM -0800, Chad Versace wrote:
>> On 02/26/2015 05:24 AM, Chris Wilson wrote:
>>> When rendering to an fbo, even though it may be acting as a winsys
>>> frontbuffer or just generally, we never throttle. However, when rende
On Wed, Mar 04, 2015 at 09:41:56AM -0800, Chad Versace wrote:
> On 02/26/2015 05:24 AM, Chris Wilson wrote:
> > When rendering to an fbo, even though it may be acting as a winsys
> > frontbuffer or just generally, we never throttle. However, when rendering
> > to an fbo, there is no natural frame b
On 02/26/2015 05:24 AM, Chris Wilson wrote:
> When rendering to an fbo, even though it may be acting as a winsys
> frontbuffer or just generally, we never throttle. However, when rendering
> to an fbo, there is no natural frame boundary. Conventionally we use
> SwapBuffers and glFinish, but potenti
When rendering to an fbo, even though it may be acting as a winsys
frontbuffer or just generally, we never throttle. However, when rendering
to an fbo, there is no natural frame boundary. Conventionally we use
SwapBuffers and glFinish, but potential callers avoid often glFinish for
being too heavy
10 matches
Mail list logo
