Tech content trusted by users in North America and around the world
6,725 Reviews & Articles | 46,135 News Posts
TRENDING NOW: AMD's dual Fiji chip spotted as Radeon R9 Gemini, is this the Fury X2?

NVIDIA's GT300 coming along well for Q4'09

NV's first DX 11 GPU shaping up well
| Video Cards News | Posted: Sep 29, 2009 3:45 am

Word's come in from the horse's mouth that NVIDIA's first DirectX 11 (GT300) GPU is shaping up okay and should make it for a Q4'09 launch, despite previous reports indicating delays and yield issues.




It seems that the GT300 has been taped out long ago and that yields are fine. This statement comes from a senior product manager for the GT300, but we also have this from our own sources [who have been saying this all along].


So where did the rumors of sub 2% yields come from? Well according to the unnamed source it looks like AMD's Competitive Analysis team mistranslated some information that stated only 9 chips per wafer worked. This information quickly spread around the internet and became what we like to call "the repeated truth". Bear in mind that this was the same team in charge of spreading rumors that Larrabee is now in its third or fourth generation of silicon, which is direly incorrect. But we'll address Larrabee and the turmoil there in a future article.



Related Tags

Got an opinion on this news? Post a comment below!
Subscribe to our Newsletter

Latest News Posts

View More News Posts

Forum Activity

View More Forum Posts

Press Releases

View More Press Releases | 522: Connection timed out

Error 522 Ray ID: 230ecce7b6e204e3 • 2015-10-06 05:00:18 UTC

Connection timed out








What happened?

The initial connection between CloudFlare's network and the origin web server timed out. As a result, the web page can not be displayed.

What can I do?

If you're a visitor of this website:

Please try again in a few minutes.

If you're the owner of this website:

Contact your hosting provider letting them know your web server is not completing requests. An Error 522 means that the request was able to connect to your web server, but that the request didn't finish. The most likely cause is that something on your server is hogging resources. Additional troubleshooting information here.