We won’t get access to FCC application internal pictures until May 13 https://fcc.report/FCC-ID/2AHYK-2212C8PRO/. Until then, unless someone cracks one open, we’ll have to guess.
Gotta open it up to look for that debug pin header connection.
My two get delivered today.
I asked that question, too, but didn't get an answer yet (I'm sure they are busy doing real work, instead of answering my dumb spec questions - which is good).
First thanks @bravenel for disclosing that info. It does a few things. First and most important it means there as has been allot of incorrect speculation in the past as it was thought it was a S905X in the newer models. It also validates some of what I was saying above.
If we go to the amlogic website it is possible to validate a few of my previous statements.
The process node did drop from 28nm to 12nm with the new chip and we did get a ARM base design bump from Coretex A53 to the A55 variant.
We can also see in the specs of those SOC's that there is potential for a good memory improvement. The older chip had a 16 bit bus and that at latest went up to a 32bit bus with up to DDR4 2666 memory.
The new SOC also seems to include a 10/100/1000 Mac so the network layer did get improved at some level.
There does seem to be a bump in the storage perspective but based on the little bit i can find online it shouldn't be to significant.
I suspect there is allot of unknown good things coming from this SOC improvement and the two marketing points do not do it justice.
Does this change potentially alleviate the jumbo frames issue that some users have run into? We know home users don't need jumbo frames and advise them to disable that...but for those who do have them enabled intentionally or otherwise, this has been a mysterious and hard to diagnose stopper for them.
The Pro still only connects 100 Mb, so I'm not as optimistic it wouldn't still be affected by jumbo frames.
That's a hard one to test in any case. When I tested it last time, the issues were intermittent so could go days sometimes without knocking the hub off the network.