If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
No, I'm saying this is a problem that didn't show up in diagnostics or while writing the proprietary driver, so there's no solution/workaround to put in the errata.
Q was claiming that there were no errata at all. Different discussion.
Yes funny in fact the open-source driver is best quality Assurance for your hardware you can get.
I'm not the smartest person in the world, but it seems that if Bridgman spent less time responding to flames, and more time coding, your issues would get fixed sooner.
Might be worth trying older versions of fglrx and see if they cause the same problem. Another remote possibility is something faulty with a card. Try another card with the same chip/stepping to see if it is reproducible.
Wait, so if AMD doesn't know what's wrong there, then how does fglrx manage to function right? There must have been some code in it that manages those cases...
Wait, so if AMD doesn't know what's wrong there, then how does fglrx manage to function right? There must have been some code in it that manages those cases...
With any bit of luck, "that part was done by the guy who left five years ago"
If it really is a hardware bug, it might be fixed in newer cards. Jerome said he was mainly running tests on r600 and r700 cards, so who knows if it's still on issue on the newer ones.
I'm not the smartest person in the world, but it seems that if Bridgman spent less time responding to flames, and more time coding, your issues would get fixed sooner.
Now wouldn't they?
Bridgman is not the one who code the driver he is a manager and his job is to communicate.
He harms nobody if he tells where to find the erratum list.
And if this is the results then I have not harmed anyone.
One the other side there is a popular movement who wants to force people in there way to communicate.
AMD Catalyst driver is more than 30 milion lines of code....... only an insane guy could think AMD really knows what they're doing inside that code after years of "put the brick on top of the previous brick and make a prayer that everything goes well." .
Comment