On Wed, Oct 1, 2014 at 2:02 AM, Chris Forbes <chr...@ijw.co.nz> wrote: > This series fixes some problems with UBO and TexBO state flagging: > > - glTexBuffer() and glTexBufferRange() never actually dirtied anything, > and so didn't work unless something else happened to dirty the correct > state (binding a UBO, or a non-buffer texture, or forcing a batch flush,.. ) > > - i965 would reemit all the texture state when a UBO changed, even though > the atom didn't actually depend on UBO state. > > - Reallocating the backing for any buffer object would cause all the > texture state and UBO state to be reemitted, even if the buffer object had > never been used as a buffer texture or a UBO. > > I noticed these issues while writing some simple test programs to explore > how Mesa+i965 behaved when the app tries to minimize driver overhead. > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Leaving the issue of how other drivers can make use of this new state flag, this series is Reviewed-by: Anuj Phogat <anuj.pho...@gmail.com> _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
