• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Discussion Mediatek SoC thread

Page 6 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
New Mediatek Chromebook SoC coming:


Say hello to the MT8189, a chip that is brand new to the Chromium Repositories and – at least according to the model number – should provide a performance bump over the Kompanio 838 (internally called the MT8188) we expect to see this fall in the Chromebook tablet named ‘Ciri’.
Where is Geralt?
 
Mediatek leak dropped:

GUbPB9FbQAEjb92.jpeg
It is very interesting that Mediatek (Fa Ge) was involved in the design of Cortex X925 (Blackhawk).

I am not extremely surprised. I watched Mediatek's Computex 2024 keynote, where the CEO hinted that they had a deep collobaration with ARM.
 
Matches the peak ST performance of the 8 Gen 3 at only 30% of the power.

30% higher peak ST performance than D9300.

The efficiency of the D9400 seems to be exceptionally good, if this rumour is to be believed.
 
GSFs8W4bcAAne4D.jpeg
The D9300's efficiency is ahead of the A17 Pro and 8Gen3 at higher wattage levels, but if you look at lower wattage levels, the script is completely flipped!

Is this the price they are paying for not having Cortex A5xx?

GSFs8TlaUAQhb6F.jpeg
The difference is there in GB5 too, though it not so drastic.
 
I am thinking how efficient will be the D9400 and the D8400.

Also D7300 started to go Quad Big... so maybe the new formation will end like this:

D9400: X Cores (4) + A7XX Cores (4)
D8400: A7XX Cores (8)
D7400: A7X/A7XX Cores (4) + A5X/A5XX Cores (4)
D6400: A7X (2) + A5X Cores (6)
 
D9400 = X (4) + A7xx (4)
D8400 = X (2) + A7xx (6)
D7400 = A7xx (4) + A5xx (4)
D6400 = A7xx (2) + A5xx (6)

(Wishful thinking).
 
D9400 = X (4) + A7xx (4)
D8400 = X (2) + A7xx (6)
D7400 = A7xx (4) + A5xx (4)
D6400 = A7xx (2) + A5xx (6)

(Wishful thinking).
Indeed, I want it too, but to be realistic...

D9400: X Cores (4) + A7XX Cores (4) - The only ones who are expecting it to keep it

D8400: A7XX Cores (8) - The best case, another case would be A7XX (6) + A5XX (2), but maybe they want to bring a fully out of order configuration ditching the in order cores. Is to me the most breaking config they delivers.

D7400: A7X/A7XX Cores (4) + A5X/A5XX Cores (4) - Realistic too since there is the D7300. Maybe the next D7400 will be Quad + Quad with Quad GPU config.

D6400: A7X (2) + A5X Cores (6) - While I want to agree with your thinking, the cost would make them stick still with that config, but maybe moving at last to A78 cores.
 
What I am more excited is the D8400, if is full 8 out of order cores, it would be a massive change in the game.
 
Mediatek should be spoiling a new Helio G40~G60 range for low-end, within six months.
- 8x APXM-6200 (Supports the bare minimum for RISC-V Android)
- DXT-8-256 (GE8320 -> DXT; 64 FP32 FLOPs/Clock -> 256 FP32 FLOPs/Clock && 4ppc -> 8ppc)
- 6nm FinFET compact (FFC) (also called N6e™)
 
Last edited:
Mediatek should be spoiling a new Helio G40~G60 range for low-end, within six months.
- 8x APXM-6200 (Supports the bare minimum for RISC-V Android)
- DXT-8-256 (GE8320 -> DXT; 64 FP32 FLOPs/Clock -> 256 FP32 FLOPs/Clock && 4ppc -> 8ppc)
- 6nm FinFET compact (FFC) (also called N6e™)
No please, no. Despite RISC-V android idea is not bad, even more, is interesting, the low tier Helio G series should rest in peace. I don't want to see the same processor being produced over and over again.

Also, In order cores should dissapear for good.
 
No please, no. Despite RISC-V android idea is not bad, even more, is interesting, the low tier Helio G series should rest in peace. I don't want to see the same processor being produced over and over again.

Also, In order cores should dissapear for good.
I kept it to the smartphone-side, but it might also replace MTK MT9026/MT9025/etcMT902x/etcMT901x for Fire TVs.
https://www.mediatek.com/products/digital-tv/mt9612
^-- whatever this thing is... all of the A53/A55 stuff will be replaced by Imagination/Imagination 2025 SOCs.

In-order cores benefit more from clustered queues: 1.5x for InO vs 1.1x for OoO. (Tremont -> Gracemont -> Skymont stuff) So, I assume In-order will be here to stay.
 
Last edited:
Dimensity 9400 arrives in Geekbench.
The single core clock seems to be limited to about 2 GHz, which explains the measly 1500 score. Assuming linear scaling, it should score 2700 at it's peak of 3.6 GHz.
 
Dimensity 9400 arrives in Geekbench.
The single core clock seems to be limited to about 2 GHz, which explains the measly 1500 score. Assuming linear scaling, it should score 2700 at it's peak of 3.6 GHz.
Seems to almost line up with ARM's presentation about X925 performance. Maybe a bit under. Extrapolate to the 3.8GHz level they were referencing, it'd be about 100 points below. Assuming linear scaling.
From: https://forums.anandtech.com/thread...verse-µarchs-discussion.2611782/post-41242907
 
Dimensity 9400 hit Geekbench again, now with the full blooded scores. 2800+ single, nearly 9000 multi.

That’s more like it. Should be ARMv9 though, maybe GB doesn’t recognize it yet.

Also, I find it interesting that the X925 would have higher IPC than the Oryon core in that leaked OnePlus result. That’s pretty impressive, almost a 6% advantage.
 
That’s more like it. Should be ARMv9 though, maybe GB doesn’t recognize it yet.

Also, I find it interesting that the X925 would have higher IPC than the Oryon core in that leaked OnePlus result. That’s pretty impressive, almost a 6% advantage.
Yeah, well, in the end power usage is what matters. If Oryon can clock higher while using about the same, then they did a better job job but we'll have to wait and see. Anyway, interesting times ahead.
 
That’s more like it. Should be ARMv9 though, maybe GB doesn’t recognize it yet.

Also, I find it interesting that the X925 would have higher IPC than the Oryon core in that leaked OnePlus result. That’s pretty impressive, almost a 6% advantage.
Yeah, I always expected X925 would have a wee bit higher IPC than Oryon.
 
It seems this generation, Dimensity has less performance than Snapdragon. So Mediatek will have to score design wins for the Dimensity 9400 on the basis that it's cheaper and more efficient (?).
 
Dimensity 9400 hit Geekbench again, now with the full blooded scores. 2800+ single, nearly 9000 multi.


That OPPO phone has been benchmarked a few times, it seems:


The highest 1T score is 2889, which is the same 1T score as the basically fastest 288V Lunar Lake run I'd seen.


Sometimes X925 is 25% slower and sometimes X925 is 25% faster. Ends up at an equal geomean with the 288V.
 
Back
Top