Separating Fact from Fiction: The Impact of Android Anti-fragmentation on the Processor Landscape
April 1, 2011
Rumors, misinformation and speculation are spreading like wildfire across the industry today following recent reports about Android anti-fragmentation efforts and what this means for processor architecture openness. Will Google’s anti-fragmentation initiatives for Android code impact providers of microprocessor architectures such as MIPS, Intel and ARM? Does anti-fragmentation mean that Google is standardizing Android for any specific architecture? As someone who has been deeply involved with MIPS’ Android efforts, here’s my take on separating some of the fact from fiction.
Related Semiconductor IP
- SoC Security Platform / Hardware Root of Trust
- SPI to AHB-Lite Bridge
- Octal SPI Master/Slave Controller
- I2C and SPI Master/Slave Controller
- AHB/AXI4-Lite to AXI4-Stream Bridge
Related Blogs
- Android Outsells iPhones, Opens Processor Market
- RISC-V's Impact on Processor IP Licensing Fees
- New Synopsys Report Highlights Key Industry Insights on the Impact of Multi-Die Systems
- Exploring USB Applications and the Impact of USB IP