[Mesa-dev] [PATCH V4 00/19] ARB_texture_multisample support
chrisf at ijw.co.nz
Fri Mar 1 11:54:37 PST 2013
I've had a quick look at the push-pop-texture-state regression, and
that looks like a real bug I've introduced. I'm looking into it.
On Sat, Mar 2, 2013 at 8:44 AM, Chris Forbes <chrisf at ijw.co.nz> wrote:
> The minmax regression is addressed by my followup series, which adds
> the internalformat_query interactions.
> Do I need to fold that into this one?
> On Sat, Mar 2, 2013 at 7:59 AM, Paul Berry <stereotype441 at gmail.com> wrote:
>> On 26 February 2013 02:10, Chris Forbes <chrisf at ijw.co.nz> wrote:
>>> This series adds the core mesa bits for ARB_texture_multisample, and
>>> in the i965 driver for Gen6 and Gen7.
>>> I've addressed the issues that were raised for V3, and also fixed some
>>> bugs which I found while beefing up the piglit coverage for this.
>>> - Proxy texture targets were denied in glTexImage*Multisample.
>>> - I was lying to the i965 fs regalloc about how many regs were written by
>>> the sampler message, so it was clobbering the results in nontrivial
>>> Things for another day:
>>> - CMS layout support on Gen7.
>>> - Verify multisample depth arrays. Until this is done, we only advertise
>>> A follow-up series addresses the interactions between this extension,
>>> multisample renderbuffer creation, and internalformat_query, which
>>> resolves the
>>> remaining TODO in 12/19.
>>> -- Chris
>>> mesa-dev mailing list
>>> mesa-dev at lists.freedesktop.org
>> I just ran this series through a full piglit run on my Ivy Bridge machine,
>> and got two regressions:
>> - spec/!OpenGL 1.1/push-pop-texture-state
>> - spec/ARB_internalformat_query/minmax
>> Are you aware of these regressions? Do you know what's causing them?
More information about the mesa-dev