Originally posted by Calinou
View Post
Announcement
Collapse
No announcement yet.
New AMD Catalyst Beta Supports Linux 3.8, TF2 Fixes
Collapse
X
-
-
Originally posted by Vim_User View PostSure, that that must be why they primarily fix gaming issues.
For Steam games, for which Ubuntu 12.04 is the recommended distro...
nvidia also has no problem given nouveau the middle finger for documentation... But a selfish, arrogant and narrow-minded company serving selfish, arrogant and narrow-minded customers, no wonder it goes well for them
Too bad the mayan calendar turned out to be an hoax, really...
Back on topic, AMD's page still lists 13.3 beta 3 from last month, it might be time to stop announcing stuff that's not officially out because some random Bozo McLame found a random URL on AMD's servers.Last edited by PsynoKhi0; 11 April 2013, 01:49 PM.
Comment
-
Originally posted by PsynoKhi0 View PostBut a selfish, arrogant and narrow-minded company serving selfish, arrogant and narrow-minded customers, no wonder it goes well for them
If AMD wants to stay competitive they should think about that.
Comment
-
Originally posted by bridgman View Post
I think you're missing the point. The priorities and goals for the binary mostly come from the workstation business unit, and WS customers are quite a bit more likely to run on stable enterprise distros.
It's not a black-and-white thing but last time I asked the workstation folks there was more customer interest in supporting RHEL 4 (!!) than in supporting the fastest moving consumer distros.
Open source drivers focus more on upstream and fast-moving distros. Originally there was a big gap between what the radeon and Catalyst drivers covered but the gap is closing over time.
I mean with the slight chance of graphic intense blockbuster games coming to Linux,
this is hard to believe...
It doesn't look like your binary guys care about RHEL bug reports either:
I hope that there is at least an active discussion how to improve on the communication with non-WS customers.
In particular the current bug-tracking system is basically defunct and highly frustrating.
P.S. Don't take it personal, I know you're not the one to blame.
Comment
-
Originally posted by entropy View PostI mean with the slight chance of graphic intense blockbuster games coming to Linux,
this is hard to believe...
Originally posted by entropy View PostIt doesn't look like your binary guys care about RHEL bug reports either:
There might be a disconnect in the sense that none of the "release" drivers for FirePro seem to meet the criteria Jammy suggested, so I suspect there's a public beta which isn't on the amd.com "released" driver site. I have updated the ticket to make it clear that there do not seem to be any drivers on amd.com which meet the criteria Jammy suggested, and so a link would help. Hopefully that will get the 6.4 users pointed to a driver they can test.
Originally posted by entropy View PostI hope that there is at least an active discussion how to improve on the communication with non-WS customers.
In particular the current bug-tracking system is basically defunct and highly frustrating.
I suspect that what you're really looking for is "more bugs being fixed". Given that, my vote would be to have them work on bugs and only respond on the board when they need more info to make progress or are aware of a solution/workaround already (current state), rather than fixing fewer issues and talking more, but that's just one opinion.Last edited by bridgman; 15 April 2013, 12:11 PM.Test signature
Comment
-
Originally posted by curaga View PostSurely AMD can afford to hire one secretary to respond to bugs with "noted, our people will take a look"
The point is that the developers do *not* have time to look at every bug individually in real time. That's why we don't tell people that we will.
The devs look for clusters of problems indicating areas that need some urgent attention, and patterns which might suggest possible solutions. You'll find this is the case at every vendor although the degree may vary.Last edited by bridgman; 15 April 2013, 12:25 PM.Test signature
Comment
-
Originally posted by bridgman View PostAhh, you mean a feel-good platitude disconnected from reality. I guess we could do that but it's not the way we like to operate. Besides, I would rather use a script for mindless responses... when we have extra $$ to spend we try to spend it on engineering folks.
The point is that the developers do *not* have time to look at every bug individually in real time. That's why we don't tell people that we will.
The devs look for clusters of problems indicating areas that need some urgent attention, and patterns which might suggest possible solutions. You'll find this is the case at every vendor although the degree may vary.
Fair enough.
From now on I will judge the support - I'll try at least - just by how long it takes the devs to fix bugs I'm facing or that I have filed.
I'd be happy to be proven wrong!
Comment
-
Originally posted by Kano View PostTest signature
Comment
Comment