Article 5YP06 Qualcomm's M1-Class Laptop Chips Will Be Ready For PCs In 'Late 2023'

Qualcomm's M1-Class Laptop Chips Will Be Ready For PCs In 'Late 2023'

by
BeauHD
from Slashdot on (#5YP06)
An anonymous reader quotes a report from Ars Technica: Qualcomm bought a chipmaking startup called Nuvia back in March of 2021, and later that year, the company said it would be using Nuvia's talent and technology to create high-performance custom-designed ARM chips to compete with Apple's processor designs. But if you're waiting for a truly high-performance Windows PC with anything other than an Intel or AMD chip in it, you'll still be waiting for a bit. Qualcomm CEO Christian Amon mentioned during the company's most recent earnings call that its high-performance chips were on track to land in consumer devices "in late 2023." Qualcomm still plans to sample chips to its partners later in 2022, a timeframe it has mentioned previously and has managed to stick to. A gap between sampling and mass production is typical, giving Qualcomm time to work out bugs and improve chip yields and PC manufacturers more time to design and build finished products that incorporate the chips. [...] Like Apple's processors, Nuvia's support the ARM instruction set but don't use off-the-shelf ARM Cortex CPU designs. These processor cores have been phenomenally successful in commodity SoCs that power everything from Android phones to smart TVs, and they helped popularize the practice of combining large, high-performance CPU cores and small, high-efficiency CPU cores together in the same design. But they rarely manage to top the performance charts, something that's especially noticeable when they're running x86 code on Windows with a performance penalty.

twitter_icon_large.pngfacebook_icon_large.png

Read more of this story at Slashdot.

External Content
Source RSS or Atom Feed
Feed Location https://rss.slashdot.org/Slashdot/slashdotMain
Feed Title Slashdot
Feed Link https://slashdot.org/
Feed Copyright Copyright Slashdot Media. All Rights Reserved.
Reply 0 comments