search for: deqp

https://bugs.freedesktop.org/show_bug.cgi?id=99532 Bug ID: 99532 Summary: Compute shader doesn't give right result under some circumstances Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

...gt; > > > Hi, > > one of the problems (the Play Store Crash) was resolved with following > commit: > > > http://git.osdn.net/view?p=android-x86/frameworks-base.git;a=commit;h=d488a6c2bbedc06fc22942555d0157e7bf09f135 > > > > Now the remaining one, affecting the dEQP-EGL multithreading tests and > > RenderThread in general, > > has been traced in the attached logs. > > > > It seams a problem similar to "a second libEGL call failing" when > > RenderThread is trying to create dri screen > > which is killed by Android...

It looks like as of Chromium 71, nouveau is completely blacklisted. I don't really see a way back from this, since they don't cite any easily reproducible issues, except that some people had some issues with indeterminate hardware and indeterminate versions of mesa. In the bug that triggered this (https://bugs.chromium.org/p/chromium/issues/detail?id=876523), where I might have slightly

From: Dave Airlie <airlied at redhat.com> dEQP-VK.sparse_resources.image_rebind.2d_array.r64i.128_128_8 was causing a remap operation like the below. op_remap: prev: 0000003fffed0000 00000000000f0000 00000000a5abd18a 0000000000000000 op_remap: next: op_remap: unmap: 0000003fffed0000 0000000000100000 0 op_map: map: 0000003ffffc0000 000000000001...

...n't think I > managed to properly track down the true reason why. I didn't want to > reach out to them with such results, as that's just further evidence > of nouveau not working perfectly. > If you want concrete bugs to fix, I highly recommend OpenGL[ES] conformance tests, dEQP, and the WebGL CTS (which is mostly a re-hash of the OpenGL ES 3.0 CTS). Google cares quite a bit about driver conformance and are much more likely to consider nouveau to be high-quality if those test suites are in good shape. Years of experience dealing with Google says that dEQP results speak m...

On Wed, May 3, 2023 at 10:07?AM Gurchetan Singh <gurchetansingh at chromium.org> wrote: > > > > On Mon, May 1, 2023 at 8:38?AM Dmitry Osipenko <dmitry.osipenko at collabora.com> wrote: >> >> On 4/16/23 14:52, Dmitry Osipenko wrote: >> > We have multiple Vulkan context types that are awaiting for the addition >> > of the sync object DRM UAPI

...sure only one of those actually executes, and the values are all merged in. This goes somewhat against the current flow, so for GM107 we do the OOB handling directly in the surface processing logic. Perhaps the other gens should do something similar, but that is left to another change. This fixes dEQP tests like image_load_store.3d.*_single_layer and GL-CTS tests like shader_image_load_store.non-layered_binding without breaking anything else. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- OK, first of all -- to whoever thought that binding single layers of a 3d image and tellin...

This approach leads to the emitters needing to know about both global and buffer, even though at that point, they are identical. I was thinking that in the lowering logic, buffer would just get rewritten as global (with the offset added), thus not needing any change to the emitters. What do you think about such an approach? On Mar 16, 2016 2:24 AM, "Hans de Goede" <hdegoede at

https://bugs.freedesktop.org/show_bug.cgi?id=97192 Bug ID: 97192 Summary: SuperTuxkart graphic errors [NVE4 - GK104] Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: other Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: