Summary: | demo arbocclude regression since r600g: Implement asyncronous query results. | ||
---|---|---|---|
Product: | Mesa | Reporter: | Andy Furniss <adf.lists> |
Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED NOTABUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
screenshot with softpipe
screenshot with llvmpipe, r600g |
Description
Andy Furniss
2011-01-30 04:58:03 UTC
(In reply to comment #0) Forgot to say this is with d-r-t kernel and git ddx on a rv790. Is this still an issue with the latest mesa from git master? for me even llvmpipe shows bottom square and corresponding text as red Using mesa (llvmpipe/r600g) up to commit 7d9e0ea7393c14cbf2d58364726951b14e0d4fc7 (glx: Properly check for a valid fd in dri2CreateScreen().) (In reply to comment #2) > Is this still an issue with the latest mesa from git master? Yes it's still the same. I don't think this is a bug, its just how the demo works, it paints red if the results aren't ready when first asked, which is perfectly within spec from what I can see. (In reply to comment #5) > Dave Airlie wrote: > I don't think this is a bug, its just how the demo works, it paints red if the > results aren't ready when first asked, which is perfectly within spec from what > I can see. I can reproduce the same result: with softpipe all squares have the same color with llvmpipe and r600g the bottom square is red Should we close this bug as NOTABUG? Created attachment 67045 [details]
screenshot with softpipe
Created attachment 67046 [details]
screenshot with llvmpipe, r600g
(In reply to comment #5) > I don't think this is a bug, its just how the demo works, it paints red if > the results aren't ready when first asked, which is perfectly within spec > from what I can see. Closing as per the comment above. |
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.