Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I have information that a next gen console will be debuting next fall. My company just got commissioned for making a next gen cpu for one of the console makers, and they need us to push it so they can make launch of next fall. Not going to disclose any more than that.
Ah yes, people with masters degrees working 17 hr a day jobs are lazy morons. You is smart. Anyone that says that devs are "lazy" just because they cant get the PS3 versions up to snuff with 360 need to STFU because they dont have a CLUE about programming, the industry, and how hard programmers have to work on their games (I work for AMD - ECE Masters - and also have a computer science minor - I've programmed an operating system and freakin know how intense it is even writing single threaded code. Multi threaded code is about 15 times as complicated at high levels.). You guys are just idiots sitting on your couch, wanting people to crap out your games without an inkling of an idea what it takes to produce it.
Also this post is interesting:
http://www.neogaf.com/forum/showpost.php?p=26403963&postcount=464
So it may be Microsoft. Trinity as CPU + a GPU. Maybe a modified Cayman@28nm..
I wonder if Sony/MS secretly collude on things like release frames or amount of system RAM etc.
I mean you wouldn't expect MS to launch in 2012 if the PS4 was going to launch in 2014.
At what cost? Launching a $400 monster power console at 18nm will enable what scale reductions and cost savings for hitting cheaper pricepoints? If there's little room to shrink, the launching price will have to remain closer to final price, which suggests something more Wii like - a smaller box launching with a more conservative spec.
Say most design decisions are done, manufacturers is selected, could ~two years be enough to push a system out? I mean the people they search may just be there make sure of proper execution of the project, to pilot it. What do you think about it?2012 would be too soon for MS given recent info.
Also this post is interesting:
http://www.neogaf.com/forum/showpost.php?p=26403963&postcount=464
So it may be Microsoft. Trinity as CPU + a GPU. Maybe a modified Cayman@28nm..
How would a 4 core Krishna compare to the current XBox offering?
What would be trinity's GPU ?
Say most design decisions are done, manufacturers is selected, could ~two years be enough to push a system out? I mean the people they search may just be there make sure of proper execution of the project, to pilot it. What do you think about it?
It makes sense for Nintendo as they haven't had a new system architecture for over a decade. They are ripe for a new system now, quite possibly ARM based and compatible with their handhelds for product synergy if they decide best power isn't of value to them (as it has proven with Wii and their handhelds).
CPU wise, probably barely faster or even slower. There was a talk some page ago about how Bobcat doesn't even competitive with XCPU in single-thread performance.. Krishna should have an enhanced version of Bobcat, but we don't expect miracles.
It wouldn't solve one of the biggest problem of Nintendo Wii: the lack of good third party support.
We could probably use the info we have on the 360 design & manufacturing timeline to get an idea of how rapid things can be.
So sure, two years would be an insanely huge amount of time if the design is done. If it's a cutting edge process, there will be problems with getting good yields - it's not just whether the chip works or not, but also getting chips at the desired clockspeeds (or rather, chips that behave within operational power and thermal designs). It'll take some time to experiment/optimize the chemical process as the console companies can't rely on binning as Intel and AMD do. Still I wouldn't expect that to take too long to fix with that sort of timeline (much less even 6months to a year) as they can focus on fixing these sorts of production issues instead of trying to push out chips as fast as possible.
On a more mature process, the problems should be pretty insignificant unless we're talking monolithic 400+ mm^2 chips. Then it's just a matter of ramping up production.
IPC is not directly comparable due to different instruction encodings.You have to remember that CISC/RISC flops aren't directly comparable because of how the architectures handle instructions. You'd also have to consider which process node and which foundry they would use to produce the CPU.
I think the preferred option is to either drop performance or respin, if possible.Aren't yields also a function of voltage as well as clockspeed? It's not just a question of how many chips simply work but also how many work at the set clockspeed and thermal parameters? So if worse comes to the worse they could go with say a vapour chamber cooler initially and then spec it down to a regular heatsink/fan combo when yields improve and required voltages drop?
IPC is not directly comparable due to different instruction encodings.
FLOPS are much more comparable, since these are operations.
The same would go for overall performance on a common workload, since in the end only the performance is apparent to a user.
I think the preferred option is to either drop performance or respin, if possible.
Changing the physical design of the product and the electrical design of the device involve re-designing and then validating it.