glamor: unexport glamor_destroy_pixmap() #1815
Conversation
|
If I recall correctly from digging around and looking at the leaked driver code, NVIDIA's DDX uses some hybrid of EXA/XAA for accelerating 2D so a change to GLAMOR shouldn't affect it in any way. |
What leaked driver code? |
Happened in 2022, the hack included driver source code from what I guess was the late 4xx series. |
Interesting. Never heard of that. After a little research of what happened, my conclusion is: a) Removing LHR limits is something that actually governments need to do, because it's fraudulent. Just like advertising more memory than actually present, etc. But there're lots of more corporations that need to stand trial for such illegitimate practice. The whole "planned obsolescence" thing IMHO also is organized fraud that needs to be criminally prosecuted. b) The reaction of NVidia management IMHO is really dumb. If they would at least release specs or driver code, at least for the older cards (where competitors can't learn anything new for their own designs anymore), they would automatically increase the long-term value of their products and their brand. Long levity and resilience is a key aspect in many industries (and becoming more important by the day). But they're explicitly positioning themselves against these, so unnecessarily hurting their own brand, w/o any practical value. Looks like they're openly inviting competitors for pushing them from their throne. |
It's only used by glamor internally, on error pathes where the pixmap has been created only partially and something went wrong. Drivers don't call this function. Signed-off-by: Enrico Weigelt, metux IT consult <[email protected]>
It's only used by glamor internally, on error pathes where the pixmap has been created only partially and something went wrong. Drivers don't call this function.
Recent proprietary Nvidia doesn't seem to reference this function. Haven't checked all the older ones yet.