Last year we hinted that another Thunderbolt revision would happen this year, with a speed bump in 2014. It turns out that's exactly what's being announced at NAB this week. Intel took the opportunity to unveil its first 2013 Thunderbolt controllers as well as tease next year's Thunderbolt spec update. As a refresher, Cactus Ridge was the codename of the Thunderbolt controllers that accompanied Ivy Bridge systems. Haswell gets a new set of controllers: Redwood Ridge.

Intel is announcing two this week: the DSL4510 and DSL4410. These two are replacements for Intel's current DSL3510 and DSL3310, with 4/2 and 2/1 (channels/ports) respectively. There are no performance changes other than official support for DisplayPort 1.2 (and thus 4K displays). If you connect either of these parts to a Thunderbolt display you still only get DP 1.1a support. There's still a PCIe gen 2 x4 interface on the other end of these controllers.

The Redwood Ridge parts should be a little cheaper as they integrate a 1V voltage regulator that used to be external. The integration also reduces board area by a bit. Power consumption is also lower at idle compared to Cactus Ridge, and disconnected power consumption is significantly lower (1mW vs. 7mW for Cactus Ridge). Redwood Ridge includes the appropriate hooks for Haswell's upcoming aggressive platform power management reductions. Ultimately this is the real focus behind Redwood Ridge. With Haswell, all components on the platform need to be more power efficient - Intel's own silicon included.

Next year Intel will introduce Falcon Ridge, the first real performance upgrade to Thunderbolt. Intel is only mentioning an increase in performance to 20Gbps, which I can only assume refers to signaling speed per Thunderbolt lane. If that's correct we'd be looking at a doubling in peak theoretical bandwidth over Thunderbolt, perhaps finally making this interface useful for external GPUs. No word on a release timeframe for Falcon Ridge, but my guess is that we'll see it debut around Broadwell (14nm Haswell shrink). Given that Haswell is a late Q2/Q3 launch at best, I'd say end of 2014 is likely for Falcon Ridge.

Dropping power, BOM cost and increase performance in the future are all great, but Thunderbolt adoption on the PC remains embarassing at best. There's a lot of finger pointing between Intel and Microsoft on this, but none of it matters to the end user. Apple continues to be the only platform player that seems to get Thunderbolt and take it seriously. If Intel wants Redwood or Falcon Ridge to matter, it needs to make sure that we actually see real adoption of Thunderbolt in the PC space - with backwards compatibility guaranteed between those devices that have been shipping on the market for a couple of years now.

POST A COMMENT

44 Comments

View All Comments

  • Kevin G - Monday, April 08, 2013 - link

    DP 1.2 support? I see this as being the gateway for Apple to finally update the Mac Pro line. They've been holding out on the Mac Pro update partially due how to implement Thunderbolt on in their professional line up. Now they have the means to get 4K output out of a single connector. I figure these controllers will be on the GPU PCB as special edition Geforce or Radeon card specific to the Mac Pro's. Reply
  • FeelLicks - Monday, April 08, 2013 - link

    I wonder if DP 1.2 support is the cause for delay of Belkin's TB Express Dock? Or is it too late for that? In which case it makes buying the Dock a very UN-future proof purchase at this time... Reply
  • repoman27 - Monday, April 08, 2013 - link

    The first and second gen Thunderbolt controllers (Light/Eagle/Cactus Ridge) were designed specifically to accompany LGA 1155 Sandy Bridge and Ivy Bridge systems. Mac Pros are Xeon based. The lack of an LGA 2011 Xeon with integrated graphics or some other graceful means of piping the DisplayPort output from the dGPU to the Thunderbolt controller is more the issue at hand. Until this past December, DisplayPort 1.2 displays weren't even available, so it's not like Thunderbolt being limited to DP 1.1a would have held the Mac Pro refresh back in any way.

    The DP 1.2 support would not be relevant to Belkin's dock, it's only useable by the host PC. There may well be some other items around the edges that have now been integrated and which make waiting for Redwood Ridge desirable, but I think Belkin's issue is more to do with drivers and engineering.
    Reply
  • Kevin G - Tuesday, April 09, 2013 - link

    Thunderbolt controllers are somewhat generic. However, a Thunderbolt add-in card for PC's hasn't reached the market for the same reasons why it hasn't appeared on the Mac Pro: tunneling video through it. Outside of socket LGA 1155 motherboards which have integrated graphics to funnel, the only other logical spot would be on a discrete video card. Neither nVidia or AMD wish to support this standard. In the case of Apple, they'd have to design their own discrete card for this purpose.

    The case for DP1.2 is simple: Apple is pushing higher resolutions and that means 4K in the professional space. Apple did this previously when they released the 30" CinemaDisplay and were the first major push for dual link DVI in the market with a special Geforce 6800 Ultra card (PC versions were initially single link DVI). Apple wants the support to be there even if most customers will reuse their existing displays with it.
    Reply
  • Penti - Monday, April 08, 2013 - link

    Ivy Bridge-EP is probably the key here simply. Nothing else happens on the Xeon side. Haswell-based system would take a sidestep for it from being a workstation. Nehalem/Westmere is still pretty powerful.

    However it's pretty ridiculous that the Thunderbolt Display monitors from Apple actually don't support a pure DP input from a Mac Pro. Not sure how they will address it in the Mac Pro, but it will probably be pretty different from their basically 4 year old machine that they didn't even bother to validate it against the new IEC 60950-1 rules. Not sure they need to address that though, their customers don't sit on Thunderbolt Displays.
    Reply
  • DanNeely - Monday, April 08, 2013 - link

    If Intel wants TB to gain any traction in the PC market they're going to have to bundle TB into at least some of their higher end chipsets. Firewire struggled to gain and maintain traction when it was a $10 extra and had performance that crushed USB1 like a bug. For every consumer task except video out USB3 is good enough which puts TB in the place where FW was after USB2 came out and cheaper USB2 devices ran FW out of the market. Reply
  • jeffkibuule - Monday, April 08, 2013 - link

    Yep, it's pretty easy for OEMs to ignore an extra $20 part for a technology almost no one uses. If Intel wants widespread adoption, they need to stick it in the chipset, but that's not going to bring them significantly more money. Reply
  • royalcrown - Tuesday, April 09, 2013 - link

    UH.....you forgot that the manufacturer also need to quit charging 50 dollars for a 3 foot cable and there needs to be actual peripherals besides pre built external hard drives. If I could replace my OWC external drive with reasonably priced TB, I would ditch FW800 in a SECOND. Reply
  • DanNeely - Tuesday, April 09, 2013 - link

    With all the electronics needed in each end of a TB cable there's never going to be a $5 monoprice version. Meanwhile the chicken and egg problem is slowing what potential cost savings are available by replacing several generic transceiver chips with a single TB specific one. Reply
  • danbob999 - Tuesday, April 09, 2013 - link

    If intel integrated Thunderbolt into the chipset, it would be a great gift to AMD since it would drive up the price of their chipsets.
    Thunderbolt is the new Firewire. It will never get mass market adoption and will be phased out with the introduction of USB4.
    Reply

Log in

Don't have an account? Sign up now