Trying to wrangle Core Animation, DirectComposition, and Wayland under a single API is making me yearn for the good old days of working around bugs in Qualcomm GPU drivers. At least I only had to work around one set of bugs…
-
-
Replying to @pcwalton
"Qualcomm GPU drivers" is like several layers of horrifying. ... why does Qualcomm even *have* a GPU?!
1 reply 0 retweets 4 likes -
Replying to @whitequark @pcwalton
Unfortunately, as you probably already know, phones
1 reply 0 retweets 1 like -
I thought it's Mali
1 reply 0 retweets 0 likes -
Replying to @whitequark @xlerb
Adreno is Qualcomm’s GPU. Adreno 200 was barely functional at all.
2 replies 0 retweets 1 like -
I thought that's the normal state of GPUs.
1 reply 0 retweets 1 like -
AMD sold them their mobile GPU division which is why Adreno is an anagram of Radeon. It used to have a lot of internal memory corruption bugs in the firmware spamming IOMMU tracebacks to the kernel log.
@ScottyBauer11 reply 0 retweets 3 likes -
Replying to @DanielMicay @whitequark and
My favorite one was that in their Adreno 200 driver, glTexSubImage2D() just did “return glTexImage2D(…)” with the arguments it was given, ignoring x and y. Yes, this usually led to segfaults.
1 reply 0 retweets 6 likes -
It’s a pretty brilliant tactic: nobody will blame the GPU manufacturers, people will just blame the game developers when the games crash! Don’t need working drivers if there’s no accountability
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.