Good for ..up to 7 years? I think...like 2017?
They stopped selling it in 2012, so 5 or 6 years is 2017 or 2018.
The 2008 is still supported by updates, and that's at the 7 year mark. If they support it again this year, it'll be 8 years.
Good for ..up to 7 years? I think...like 2017?
I would be shocked if they released a new one this year. My Guess it it's still 2 years away.
They stopped selling it in 2012, so 5 or 6 years is 2017 or 2018.
The 2008 is still supported by updates, and that's at the 7 year mark. If they support it again this year, it'll be 8 years.
http://gpuopen.com/welcometogpuopen/
Good lecture.
Interactive library for compute tools, libraries, etc, etc.
Well played AMD, well played.
Indeed, CPUs are not the issue here. GPUs are, and I believe they're sorting out, or even considering if they should do it, this TB3 and DP1.3 problem. They probably really want to release something that is not a workaround but rather a proper solution, no compromises. And officially this is not possible, at least that I know of.
Intel supports only DP1.2 in TB3, so either they do a TB3.1 update or Apple does something proprietary.
The reasonable solution, although not the best, is doing 2 DP1.2 MST, as on the iMac. But they know this is not optimal, and I'd also like to see a SST solution.
That's why the nMP keeps getting delayed, no tech available yet for the machine they want to build, perfect as they see it.
Funniest part is that on other forums people already asked: "How long till people will say that AMD should now work on their drivers?"Now if only they would spend a little more time on their drivers everything would be peachy
Funniest part is that on other forums people already asked: "How long till people will say that AMD should now work on their drivers?"
As I said in another thread, I'm mostly agnostic when it comes to OS and I've both used AMD and NVidia interchangebly over the year. But the drivers situation in regard to AMD on Linux is too painful to endure. I know that they have started a new project concerning those but they don't assign enough ressources to it in my opinion making NVidia the only real choice for hardware accelerated graphics on Linux.
AMD released full new drivers full open-source AMDGPU, the only catch is that those drivers are only for newer models, (Fiji, Carrizo, Tonga, Stoney, and Iceland chipset).Isn't that on Linux AMD Drivers are OpenSource?
On the contrary, I have just had display driver shutdown on Linux for my GTX980, and the same happens on Windows side.
So no, every producer has to work on their drivers.
Isn't that on Linux AMD Drivers are OpenSource?
On the contrary, I have just had display driver shutdown on Linux for my GTX980, and the same happens on Windows side.
So no, every producer has to work on their drivers.
Isn't that on Linux AMD Drivers are OpenSource?
On the contrary, I have just had display driver shutdown on Linux for my GTX980, and the same happens on Windows side.
So no, every producer has to work on their drivers.
So I don't think if ever usb-c will support Dp 1.3, and indeed the near future will be difficult to find GPU supporting dp 1.3 unless using another interface.
It is not only my case. Currently there is a stack of complaints about Nvidia GPU display drivers crashing constantly regardless of platform. Today I have watched a gameplay footage captured with dual GTX980's when the problem appeared while it was captured. I read today a thread about GTX970 loosing display signal thanks to faulty drivers.Are you basing your opinion on a single use case, yours?
Do a search or go to some Linux forum and ask around you'll see what I mean. Eh, I'm not here to bash AMD on this, I'm only acknowledging a plain fact, that on Linux AMD drivers suck. Maybe they could fix them by putting a few more dev to debug them...
It is not only my case. Currently there is a stack of complaints about Nvidia GPU display drivers crashing constantly regardless of platform. Today I have watched a gameplay footage captured with dual GTX980's when the problem appeared while it was captured. I read today a thread about GTX970 loosing display signal thanks to faulty drivers.
All I said is that BOTH of GPU producers have to work on their drivers. I did not disagreed with you on the topic of AMD drivers, because I do not have knowledge of that. But I do have a lot of knowledge what is going on with Nvidia drivers currently.
I will completely ignore the part about AMD, because it is not my part of interest. I do not simply have knowledge about it.Again those are single point on a chart, not a proof of instability. Most of those gamer are overclocking their cards passed what is recommended. This is what brings instability, not the drivers.
I will completely ignore the part about AMD, because it is not my part of interest. I do not simply have knowledge about it.
No. The problem with loosing display signal is caused by faulty Nvidia drivers. The problems with display drivers crashing is caused by faulty drivers. Threads on Nvidia forums are full of pissed people who for example RMA'd GPUs for 4 times in a row and still got the same thing. The clocks have not been touched. I have not OC'ed my GPU and still got driver crashes. Is it also my fault that my drivers are crashing constantly?
So, DP on USB-C/TB3 is limited to passive cables either DP 1.2 or 1.3, the latter only can run 3FT on usb-c cables which makes it impractical unless you wanna dock an laptop or an pc at this short distance.You're making a misstatement here. USB-C of course supports DP 1.3. All usages of USB-C whether for DP or TB3 have issues related to length of passive cables. Longer runs will require active cables.
DP can not run on active cables, read the link I posted from ArstecnicaI didn't say TB3 is DP1.3 or anything like that. DP1.3 is supported in DP Alt Mode over USB-C, but not officially so in TB3, this is what I was saying.
Intel or Apple could make it work also on TB3, I guess, if they wanted to.
I could see a TB3D with a 1m passive cable, or longer active one. Would you see a problem here?
Please read the link from arstecnica "DP alt mode is only supported on passive cables"
So, DP on USB-C/TB3 is limited to passive cables either DP 1.2 or 1.3, the latter only can run 3FT on usb-c cables which makes it impractical unless you wanna dock an laptop or an pc at this short distance.
USB-C as Thunderbolt 3 are intended mostly for consumer applications, and 5K Display are associated with pros, notwithstanding the challenge a single usb-c can drive a 5K display just only on MST and disabling all other functionality (usb or Thunderbolt), that will be the price to support 5K on USB-C, That's why I insist the next 5K cinema display will not be Thunderbolt (unless has an integrated gpu to offload the host from GPU processing).
Whatever the nnMP will have 4 TB3/USB-C and another 6 USB3 (maybe having 2 usb-c non-thunderbolt but with DP alt mode capabilities to enable 6 5K displays as the nMP can drive up to 6 4K).
Yes, I can read the link from arstecnica, a DP 1.2 MST at HBR can run at 2mt.You can't run a 5K display over a longer passive TB3 cable than you can a DP1.3 cable, full stop. The Intel documentation supports this.