+void
+brw_blorp_blit_program::manual_blend_linear(unsigned num_samples)
+{
+ if (key-tex_layout == INTEL_MSAA_LAYOUT_CMS)
+ mcs_fetch();
This won't work. The MCS value we fetch has to match up with the pixel
that we're sampling from. Since this function samples from
On 26 June 2013 19:41, Anuj Phogat anuj.pho...@gmail.com wrote:
On Tue, Jun 25, 2013 at 10:27 AM, Paul Berry stereotype...@gmail.com
wrote:
On 19 June 2013 19:45, Anuj Phogat anuj.pho...@gmail.com wrote:
Current implementation of ext_framebuffer_multisample_blit_scaled in
i965/blorp
On Tue, Jun 25, 2013 at 10:27 AM, Paul Berry stereotype...@gmail.com wrote:
On 19 June 2013 19:45, Anuj Phogat anuj.pho...@gmail.com wrote:
Current implementation of ext_framebuffer_multisample_blit_scaled in
i965/blorp uses nearest filtering for multisample scaled blits. Using
nearest
On 26 June 2013 14:57, Anuj Phogat anuj.pho...@gmail.com wrote:
On Tue, Jun 25, 2013 at 10:27 AM, Paul Berry stereotype...@gmail.com
wrote:
This seems like a lot of work to accomplish what is effectively a lookup
table. If this winds up becoming a performance bottleneck, you might
want
On Tue, Jun 25, 2013 at 10:27 AM, Paul Berry stereotype...@gmail.com wrote:
On 19 June 2013 19:45, Anuj Phogat anuj.pho...@gmail.com wrote:
Current implementation of ext_framebuffer_multisample_blit_scaled in
i965/blorp uses nearest filtering for multisample scaled blits. Using
nearest
On 19 June 2013 19:45, Anuj Phogat anuj.pho...@gmail.com wrote:
Current implementation of ext_framebuffer_multisample_blit_scaled in
i965/blorp uses nearest filtering for multisample scaled blits. Using
nearest filtering produces blocky artifacts and negates the benefits
of MSAA. That is the
Current implementation of ext_framebuffer_multisample_blit_scaled in
i965/blorp uses nearest filtering for multisample scaled blits. Using
nearest filtering produces blocky artifacts and negates the benefits
of MSAA. That is the reason why extension was not enabled on i965.
This patch implements
