Kaby Lake
When the fuck are they announcing the processors?
What's there to announce? It's a skylel refresh.
>>52343920
It's a tick, not a tock.
Also it's 14 nm.
>>52344019
If it's 14nm it's not a tick.
It's the same shit as Devil's Canyon, but with more stuff in the southbridge.
Kaby Lake will add native USB 3.1 support, whereas Skylake motherboards require a 3rd-party add-on chip in order to provide USB 3.1 ports.[3] It will also feature a new graphics architecture to improve performance in 3D graphics and 4K video playback.[4]
Kaby Lake will add native HDCP 2.2 support.[5]
Kaby Lake will add full fixed function HEVC Main10/10bit and VP9 10bit hardware decoding.[6]
>>52344176
yes, it's a tick.
Defil's Canyon was 22 nm.
>>52344199
But Skylake was 14nm, and Kaby Lake is the refresh of Skylake.
Yeah it is a tick
Broadwell had a few 14nm CPUs released on the desktop
Skylake main 14nm desktop launch.
And now we soon have kaby lake.
http://www.anandtech.com/show/9320/intel-broadwell-review-i7-5775c-i5-5675c
>>52344474
You know tick means 'die shrink of the microarchitecture'
There's no die shrink, no tick.
There's no change in microarchitecture, no tock.
>>52343840
and also 3D XPoint
https://en.m.wikipedia.org/wiki/3D_XPoint
>>52344199
No, they said they can't tick yet, because "muh development issues" and that cannonlel will be a tick.
tfw reading marketing drivel
muh ticks
muh tocks
nigger stfu
>>52344187
I don't see any USB 3.1 on the Kaby Lake CPU there. Only on the PCH of the Y-series. The SoC Kaby Lakes only have 3.0: sucks to be their tablets having to put USB-C connectors on USB 3.0 in 2016 when Samsung and Qualcomm will both be shipping 3.1. Only 2 memory channels. And still only gigabit eth. No 10gig. Intel make the chipset, but still don't want to include it.
I don't see the right bus for 3D X-Point support in there.
Looks like it's barely touching the processor, and spoiler alert: the 'new graphics architecture' is PowerVR Wizard, which means proprietary drivers like Broadwell.
Intel's failure to 'tock' means AMD's going to be on a similar process node and will finally have the chance to catch up with Zen.
This could be very interesting.
>>52345256
but then it's bad for us.