[Mesa-dev] Clover Platform Naming

Francisco Jerez currojerez at riseup.net
Sun Aug 3 01:45:03 PDT 2014


Aaron Watry <awatry at gmail.com> writes:

> Hi list,
>
> I was starting to look into getting cppamp-driver-ng working with
> mesa/clover, and I quickly ran into a question...
>
> cppamp-driver-ng explicitly lists which platforms are supported in its
> OpenCL back-end's source code. I went to add in the Mesa/Clover
> entries, and discovered that we're actually reporting ourselves as:
> CL_PLATFORM_VENDOR="Mesa"
> CL_PLATFORM_NAME="Default"
>
> The way that cppamp-driver-ng is written, they don't really care about
> the vendor so much as the platform name, and "Default" is about as
> generic as you can get.
>
> At this point in the game, are we stuck with this platform name, or
> would we be able to change this to "Clover" (or something more
> appropriate)?
>

I don't know of any application that relies on our platform name.  I'd
be fine with changing it to something more meaningful.

> Just wanted to ask around and see what people thought.
>
> --Aaron
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 212 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20140803/39dad7a6/attachment.sig>


More information about the mesa-dev mailing list