3 ms·
That's consolidating some controllers. It probably has more to do having fewer parts, fewer vendors, and better repair lock-in. It's not really an architectural
by dehrmann 7y ago
That's consolidating some controllers. It probably has more to do having fewer parts, fewer vendors, and better repair lock-in. It's not really an architectural step towards replacing the CPU--it's a southbridge with better marketing.
- josteink 7y ago> It's not really an architectural step towards replacing the CPU--it's a southbridge with better marketing. Except it locks out any OS not Windows or MacOS from using it. Southbridge didn’t have hardware mechanisms in place to intentionally lock Linux out from using the machine’s (rather expensive) internal storage.
- sa1 7y agoIt doesn't lock out linux from using it. They deviated from the NVMe spec, and it took time(and somebody to actually investigate) for the linux guys to figure it out: https://github.com/Dunedan/mbp-2016-linux/issues/71 https://github.com/Dunedan/mbp-2016-linux/issues/71 It's not a lockout by any means, and your next version of linux kernel will support it just fine(assuming the NVMe patches are merged).