Add v3d to Rusticl
Initial support for rusticl was added to the Broadcom v3d driver some time back so update the matrix to reflect that.
@nullr0ute I don't see v3d in the Rusticl section in https://gitlab.freedesktop.org/mesa/mesa/blob/main/docs/features.txt
I can't add drivers that are not present in this file.
@MightyCreak I looked at that file but don't see where in the rusticl section where to explicitly list a driver, all the drivers that are listed are against specific sub features, can you provide a line where the drivers are listed?
Gentle ping here :) AFAICS this is in line with https://github.com/MightyCreak/mesamatrix/pull/310, i.e. should be able to land as is.
@nullr0ute @rmader I don't have control over the features.txt file. It's up to the mesa developers to update this file and add v3d somewhere in the Rusticl section.
This file was not meant to be formatted in the first place, so it lacks some structure and standardization. The way I determine the drivers of an API is simply to look at which ones are explicitly written in a section, i.e. after the -- all DONE: line, or at the end of each extension line.
In the case of Rusticl, the developers didn't fille the all DONE parts, so whenever an extension is flagged DONE, I can't really know which drivers they are talking about.
I'll close this PR as it doesn't seem that the Mesa devs are adding v3d to Rusticl. It can be reopened in case v3d is finally added.
It was added, before I even filed this PR.
I'm pretty sure the intended sentence was:
...it doesn't seem that the Mesa devs are adding v3d to Rusticl section of the features.txt file
Yep, mesmatrix can only show what features.txt contains.
Do I understand correctly that this would need Mesa to e.g. add v3d and other drivers to the all DONE: lists, like it does for other sections?
Do I understand correctly that this would need Mesa to e.g. add v3d and other drivers to the
all DONE:lists, like it does for other sections?
yep! either in the all DONE: if indeed all the extensions are done for the API version (e.g. Rusticl OpenCL 3.0), but you can also be more granular and add the driver per extension (e.g. DONE (v3d)).