On 10/01/2014 12:00 PM, Neil Roberts wrote:
> It shouldn't be necessary to flush the context within the driver
> implementation because the old context is explicitly flushed in
> _mesa_make_current before the driver code is reached. It is useful to only
> have a single place that flushes the contex
Ian Romanick writes:
> I'm a little bit skeptical of this. _mesa_make_current doesn't call
> intelMakeCurrent. intelMakeCurrent calls _mesa_make_current, and it
> calls _mesa_make_current much later in this function. By the time
> _mesa_make_current is called, a bunch of driver state has been
It shouldn't be necessary to flush the context within the driver
implementation because the old context is explicitly flushed in
_mesa_make_current before the driver code is reached. It is useful to only
have a single place that flushes the context when switching contexts to make
it easier to later
