Remember when SemiAccurate said Nvidia shuffled their Tegra lineup to insert a stopgap A9 part? Remember when SemiAccurate said it would delay the real T40 based Tegra 4? Remember when SemiAccurate said Nvidia would put out a reference phone? Guess what happened?
While we hate to dredge up old news, it seems that some people didn’t actually believe us when we laid out the tale of woe that was T30, T33, T35, and T40, the attendant delays, and the dysfunctional management moves that made it so. Well, today Nvidia announced their Tegra 4i SoC and a reference phone design called Grey to go with it. It all sounds so eerily familiar, almost like SemiAccurate nailed every point about it, and the semi-official Nvidia backchannel denials were as honest as their official denials.
OK, enough patting ourselves on the back, lets take a look at what is going on here. If you read the write-ups of the Grey/Tegra 4i announcements like this one at Ars, there are a few things that become clear. First is Nvidia is up to their old ways when quoting speeds, the chip is called a 2.3GHz part even though that is just the max turbo frequency of a single core with the others cores off. Sustained frequency or that of more than a single core is far lower and undisclosed.
The process Grey is made on was also not disclosed, but it almost assuredly a 28nm chip. A 33% top clock rate bump without raising TDPs to an unacceptable level is pretty much impossible without a shrink. Also, the GPUs are said to be the same as the T40 version of Tegra 4, ie the A15 cored new one. That is a 28nm part and is again extremely unlikely that those units would be backported to an older 40nm process just for this chip. Last is the anecdotal evidence of the relative die sizes Nvidia was showing on the launch slides. While the die shots themselves are almost assuredly faked, the scaled die is a familiar PR move by the company.
Related to the GPU side of things is what SemiAccurate said in October of 2011 when we exclusively told you about the T35/Tegra 4i/Grey project. We said that it was a stopgap hack that would put the A9 cores back in to the T40, pushing out that chip and ending up with a Frankenstein hack. Today we got exactly that, A9 cores in a T40 uncore, or at least most of the uncore, some of the shaders fell by the wayside to make room for the Icera modem.
Overall, the chip is a mixed bag of good and bad. At this point the cores are painfully outdated, the A15 was last years news, the A9 in the T4i made headlines in 2009. For CPU power this part is DOA. On the GPU side though, depending on how well the new shaders do, it may not embarrass itself there, but the Tegra 4i won’t win many graphics crowns due to it’s lack of programmable shaders. If the memory bandwidth from the uncore is a big step up from that in the Tegra 3/T30/T33, it will do just fine. If not, Tegra 4/T40 is in deep trouble. The modem, if the bugs that crippled the Asus Transformers late last year were fixed, will be quite solid. SemiAccurate thinks it will be just fine by the release date.
Technical items aside, there is one big problem with the unveiling of Tegra 4i/T35/Grey and more importantly of the Phoenix phone reference design. As we said two days ago, it points to some very fundamental problems that the entire Tegra line has, and the grim outlook surrounding it’s future. Worse yet is the name, Tegra 4i is a big flashing red flag for anyone in the financial world, pay very close attention to why Nvidia chose this naming convention.
Note: The following is analysis for professional level subscribers only.
Disclosures: Charlie Demerjian and Stone Arch Networking Services, Inc. have no consulting relationships, investment relationships, or hold any investment positions with any of the companies mentioned in this report.
Latest posts by Charlie Demerjian (see all)
- AMD talks Threadripper, Ryzen Mobile, and Ryzen Pro - May 22, 2017
- AMD calls Naples Epyc during Analyst Day - May 17, 2017
- Intel’s new Scalable Xeon branding is just a price increase - May 5, 2017
- Are consumer PCs safe from the Intel ME/AMT exploit? - May 3, 2017
- Remote security exploit in all 2008+ Intel platforms - May 1, 2017