Processors for Chromebooks, AMD could make them at 4 nanometers from Samsung

Processors for Chromebooks, AMD could make them at 4 nanometers from Samsung

According to one widespread note from a JP Morgan analyst to his clients, AMD will address to Samsung for the future production of chips for Chromebooks with production process a 4 nanometers. The investment bank also does not rule out the possibility that AMD will rely on Samsung Foundry for the future GPU production.

“Our research indicates that AMD may outsource Chromebook CPUs to Samsung and its 4-nanometer process, likely ready for mass production in late 2022, as TSMC would have limited capacity to allocate to Chromebook projects given the decline in market demand, “wrote analyst Gokul Hariharan.

However, a debate has been unleashed on this item, in fact there is a debate on the economic logic. AMD should in fact adapt the design of its APUs for Chromebooks to Samsung’s production chain and the operation could be expensive. The demand for Chromebooks, after the peak of the past months linked to the purchase of devices for the DAD and remote work, is in fact waning.

Read This Now:   As if the RX 6500 XT was not enough, the RX 6400 is coming, and the return of the RX 560

It is therefore likely that if AMD decides to turn to Samsung, it will not only be for APUs destined for Chromebooks but also for other products, such as some GPUs. “Furthermore, we believe that AMD could evaluate some projects, probably on the GPU front, for production at Samsung at 3 nanometers in 2023-2024, but most of the major platforms – CPUs for servers, mobile and desktop – are likely to remain within the 3 nanometer range of TSMC. “

Gift ideas, why waste time and risk making mistakes?
GIVE A GOOD AMAZON
!


Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5420

Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5420