1783513 - DeviceFamily::QualcommAll does not include SC7180 Adreno 618 GPUs

Status: UNCONFIRMED

(Core :: Graphics, defect, P2)

Description

[Leonard Lausen]

Steps to reproduce:

Tested nightly builds from https://bugzilla.mozilla.org/show_bug.cgi?id=1783053 on a device with Adreno 618 GPU. Those builds add APPEND_TO_DRIVER_BLOCKLIST_EXT for DeviceFamily::QualcommAll disabling nsIGfxInfo::FEATURE_DMABUF_SURFACE_EXPORT and nsIGfxInfo::FEATURE_DMABUF_SURFACE_EXPORT respectively.

Actual results:

about:support shows DMABUF_SURFACE_EXPORT and DMABUF respectively as available by default.

Expected results:

about:support should have showed DMABUF_SURFACE_EXPORT and DMABUF respectively as blocked by default: Blocklisted by gfxInfo.

Comment 1

[Robert Mader [:rmader]]

Note for myself: see bug 1696691 comment 11 for about:support, including vendor/device IDs.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

[Brad Werth [:bradwerth]]

Andrew, can you figure out why Adreno 618 isn't being detected as a Qualcomm device? Or isn't triggering the disabling of DMABUF_SURFACE_EXPORT?

Comment 4

[Robert Mader [:rmader]]

FWIW: neither vendor ID (0x3b90) nor deviced ID (0x3200) are to be found in the sources ATM. Not sure though if we even want to start with device IDs - or at least only use them for blocklisting, not allowlisting.

Comment 5

[Robert Mader [:rmader]]

While it would be a nice to have to fix this, IMO if DMABUF_SURFACE_EXPORT turns out to be problematic on this driver as well, it maybe makes sense to just disable it for all Mesa drivers (we already do for Intel and AMD, which are likely the most robust ones).

Maybe the feature is simply broken and needs a more solid replacement (this was suggested to me by gstreamer devs where the used extension is known to cause problems as well).

Comment 6

[Leonard Lausen]

I have not noticed issues running with DMABUF_SURFACE_EXPORT on Adreno 618. What kind of issues are happening on Intel and AMD?

Comment 7

[Robert Mader [:rmader]]

(In reply to Leonard Lausen from comment #6)

I have not noticed issues running with DMABUF_SURFACE_EXPORT on Adreno 618. What kind of issues are happening on Intel and AMD?

E.g. bug 1774271 or bug 1778114