AMD Cancels 28nm APUs, Starts From Scratch At TSMC
MrSeb writes "According to multiple independent sources, AMD has canned its 28nm Brazos-based Krishna and Wichita designs that were meant to replace Ontario and Zacate in the second half of 2012. The company will likely announce a new set of 28nm APUs at its Financial Analyst Day in February — and the new chips will be manufactured by TSMC, rather than its long-time partner GlobalFoundries. The implications and financial repercussions could be enormous. Moving 28nm APUs from GloFo to TSMC means scrapping the existing designs and laying out new parts using gate-last rather than gate-first manufacturing. AMD may try to mitigate the damage by doing a straightforward 28nm die shrink of existing Ontario/Zacate products, but that's unlikely to fend off increasing competition from Intel and ARM in the mobile space."
So far I have been totally unable to tax my current CPU past 40% utilization. I think we can take a break and let software catch up and older systems fall off the support map before the next generation of CPUs hit.
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
Moving 28nm APUs from GloFo to TSMC means scrapping the existing designs and laying out new parts using gate-last rather than gate-first manufacturing. AMD may try to mitigate the damage by doing a straightforward 28nm die shrink of existing Ontario/Zacate products, but that's unlikely to fend off increasing competition from Intel and ARM in the mobile space
After reading the summary (a few times), I came to the conclusion that I know nothing about this topic. Thanks for the heads up so I that was not burdened with reading an article that only a select few might understand or care.
Flexible bare-metal recovery for Linux/UNIX
Your assumption that you can simply ignore AMD's influence in the CPU market and still end up with a relevant model to explain and predict its outcome is both naive and disingenuous. AMD does have products which outperform equivalent Intel products, even when not accounting with Intel shenanigans such as relying on funny compiler tricks, and AMD happens to price them quite attractively. If you haven't considered any AMD offering on any budget for any serious desktop and instead opted to rely only on Intel products then you are both clueless and economically-challenged.
Slashdot, fix your code or at least hire someone who is competent at it to do it for you.