Bug 110253 - glBlitFramebuffer fails on MSAA fbo source.
Summary: glBlitFramebuffer fails on MSAA fbo source.
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/swr (show other bugs)
Version: 19.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-27 06:37 UTC by Haipeng Wang
Modified: 2019-09-18 18:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Haipeng Wang 2019-03-27 06:37:26 UTC
https://github.com/mesa3d/mesa/blob/master/src/gallium/drivers/swr/swr_screen.cpp#L908
https://github.com/mesa3d/mesa/blob/master/src/gallium/drivers/swr/swr_screen.cpp#L105

when using MSAA fbo as read source, and OSMesa framebuffer as target, glBlitFramebuffer fails。

swr_blit: color resolve : 8 -> 0
swr: blit unsupported r8g8b8a8_unorm -> r8g8b8a8_unorm

I think it may be solved by setting nr_storage_samples to 0 in src/gallium/drivers/swr/swr_screen.cpp swr_create_resolve_resource

      /* Create a single-sample copy of the resource.  Copy the original
       * resource parameters and set flag to prevent recursion when re-calling
       * resource_create */
      struct pipe_resource alt_template = msaa_res->base;
      alt_template.nr_samples = 0;
      alt_template.nr_storage_samples = 0;
      alt_template.flags |= SWR_RESOURCE_FLAG_ALT_SURFACE;
Comment 1 Bruce Cherniak 2019-04-02 16:13:09 UTC
Thank you for reporting this bug and a possible solution.  We will investigate.
Comment 2 Gregory Popovitch 2019-04-12 15:38:01 UTC
Could this possibly affect the AMD Radeon Pro 19.Q1.1 drivers?
Comment 3 Bruce Cherniak 2019-04-17 18:04:32 UTC
The patch is OpenSWR specific, however, it is in response to a gallium API change:
"gallium: add pipe_resource::nr_storage_samples, and set it same as nr_samples"

https://cgit.freedesktop.org/mesa/mesa/commit/?id=8632626c81a09315276d7defa63092247d7fd308
Comment 4 GitLab Migration User 2019-09-18 18:24:44 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/202.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.