- Joined
- Jun 20, 2024
- Messages
- 372 (2.40/day)
There might be some overlap - my point is two-fold - in that this could be combined to scale up the Ryzen 5 and 7 range to encompass c cores also, be it 4c + 4/6/8 combos. If Intel continue to throw increasing numbers of e cores at the desktop to shore up the thread counts, AMD will at some point need to do something.Problem is now your spinning a completely new IO die for a specific segment of the market
Currently this is why their chiplet approach works as they can mix and match parts to suit from bare office PCs all the way up to highest end server parts with very little changing between them. For AMD this is the best in terms of mass productions benefits. I believe for their whole current offerings its 2 IO dies, 2 CCD types and 1 Monolithic die to cover all these?
Instead of what you are saying in regards to reworking of the IO Die. I suspect there will be a repurpose of some of their mobile offerings to fill the low end office pcs, especially with the explosion of USFF PCs becoming more and more common in office spaces.
The other option is to do chiplets with either all c cores or a mix on the desktop parts, but as is the case with the current AM5 platform I don't see that making it price into the low-end/low-cost price point - AMD will be merely redefining their version of it at a higher cost price.
To be honest the repurposing of mobile dies into USFF devices isn't new for either Intel or AMD, but the current Pheonix dies used for the 8000 series desktop parts are a bit 'meh' in terms of utilising the desktop platform, especially if you wanted to use a PCIe x16 card for anything. And at the current pricing, Intel will still shift more i3's to people who don't care about how good the iGPU is, which when you get to the 8300G isn't the huge step offered by the 8700/8600 parts, and at that price point the i3 is a better CPU also.
Unfortunately, 'AI' is the new buzzword and I suspect the likelihood is the next IO die they come out with will probably have their 'not-actually-AI' logic block added to it before anything else so as to satisfy Microsoft's dumb requirements that require 'still-not-really-AI' and that it be performed by dedicated logic instead of processed by perfectly capable iGPU or dGPU hardware...