[Bug 30776] New: Wine expects GL_VENDOR to identify the card vendor

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Oct 11 12:38:15 PDT 2010


           Summary: Wine expects GL_VENDOR to identify the card vendor
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: trivial
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel at lists.freedesktop.org
        ReportedBy: seppo.yli-olli at iki.fi

Not sure whose bug this is but Wine's logic for figuring out which card we have
currently uses the following piece of code to figure out which "hw_vendor" we
   if (strstr(gl_vendor_string, "ATI")
            || strstr(gl_vendor_string, "Advanced Micro Devices, Inc.")
            || strstr(gl_vendor_string, "X.Org R300 Project")
        || strstr(gl_renderer, "R100")
        || strstr(gl_renderer, "R200")
            || strstr(gl_renderer, "R300")
            || strstr(gl_renderer, "R600")
        || strstr(gl_renderer, "R700"))
    return HW_VENDOR_ATI;
Now, this wasn't such a problem with classic driver, eg with r600c we had even
double positive match. With r600g, however, renderer string says the exact chip
name (which Wine uses after it has found the right branch of chip id's to
search from) and GL_VENDOR is "X.org". This causes Wine to fail detection (and
end up fallbacking in a rather boring fashion through HW_VENDOR_NVIDIA finally
to Nouveau since it already *did* manage to detect that we're running Mesa).
I'm not sure what exactly the GL_VENDOR string should say but I'm hoping
something more distinguishing could be put there. The first two items in that
list would imo be viable options but that's not to say something else couldn't
be put in and make Wine detect "hw_vendor" based on that instead.

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the dri-devel mailing list