Published in PC Hardware

Intel Cannonlake 10nm delayed beyond 2016

by on08 July 2015


Just as well it has no rivals 

A couple of weeks ago we said that Intel was delaying its Cannonlake processors and its next-generation Kaby Lake processors.

These were originally scheduled for early 2016, reportedly will be pushed back until September 2016 for the consumer version and January 2017 for the enterprise one.

What it looks like now is that Chipzilla will launch its 14nm Skylake processors for desktops in August and for notebooks in the fourth quarter. Cannonlake, originally planned to directly succeed Skylake in 2016, have been postponed and Intel has inserted the 14nm Kaby Lake platform between them as a buffer. The enterprise version of Kaby Lake processors being postponed to 2017.

This is starting to look like a spectacular mess. Notebook brand vendors which are usually in May-July, have been delayed by 3-6 months. Dell's process for its Kaby Lake-based enterprise notebooks is expected to start in January 2016.

Most brand vendors will start on the consumer version of Kaby Lake between July-October 2016.

All this is making Kaby Lake a little more important than many thought. Earlier it was believed that the "Kaby Lake" was just a temporary solution in order to refresh Intel's product lineup before all-new 10nm "Cannonlake" chips hit the market, which is something that happened to "Broadwell". It now appears that the "Kaby Lake" is a product family that will be Intel's primary product lineup for a long time.

Such launch schedule indicates that the world's No. 1 maker of microprocessors will not release its 10nm chips until sometimes in 2017.

Normally Intel would be worried about someone else, such as AMD stealing its thunder, but in this case its rivals have troubles of their own so it might just get away with it. Sure it might hack off some of its venders, but it has time to get its process schedule right thanks to its rivals dropping the ball.

 

Last modified on 16 July 2015
Rate this item
(12 votes)

Read more about: