On 23 February 2018 at 13:55, Thierry Reding <thierry.red...@gmail.com> wrote: > On Thu, Feb 22, 2018 at 02:32:26PM +0000, Emil Velikov wrote: >> On 22 February 2018 at 13:23, Thierry Reding <thierry.red...@gmail.com> >> wrote: > [...] >> > Good point. Let me check what exactly we use in the closed-source driver >> > and then come up with a proposal. >> > >> > I think perhaps a good choice for the vendor would be "grate". Even >> > though this driver isn't part of the grate project, I'm hoping that we >> > will eventually see Erik's and Dmitry's work merged into this. >> > >> > Adding Erik and Dmitry to get their opinion. >> > >> Ack. Since this can be tweaked later, I'd suggest not blocking the >> series on the name specifics. > > So the closed-source driver reports this: > > ... > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: NVIDIA Tegra X1 (nvgpu)/integrated/DEBUG > ... > > I suppose we could just do: > > vendor = "tegra" > name = "NVIDIA Tegra X1" > > The vendor seems to match the driver name for all (to match the Mesa driver > name like other > drivers do) > we can base the name on something we could query from sysfs, for > example. So we could display "NVIDIA Tegra 20" and similar for the GPU > supported by grate and K1, X1, X2, ... for those supported by Nouveau. > Quick grep though Wine and Mesa shows the following vendor strings/patterns.
Wine _patterns_ - binary drivers - ATI, NVIDIA - open source drivers/vendors - Advanced Micro Devices, Inc., VMware, Inc.., Intel, Tungsten Graphics, Inc - projects/individuals - Mesa, X.Org, DRI R300 Project, Brian Paul, Nouveau, nouveau A few extra strings from Mesa - etnaviv, freedreno, Broadcom, Red Hat In hindsight, using a single vendor 'Mesa' string would have have been useful for app developers. That ship has sailed and the suggestions sound perfectly reasonable IMHO. HTH Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev