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
- TSMC 7nm 0V75 / 0V9 ESD Local Clamp – Low Cap
- TSMC 65nm 3V3 ESD Local Clamp – Rad Hard
- TSMC 5nm 1V8, 1.2V and 0.9V ESD Local Protection – Low Cap
- TSMC 3nm 3V3 ESD Local Clamp
- TSMC 3nm 1V2 ESD Local Clamp – Low Capacitance
Related Blogs
- Android Outsells iPhones, Opens Processor Market
- Enhancing Edge AI with the Newest Class of Processor: Tensilica NeuroEdge 130 AICP
- The Role of GPU in AI: Tech Impact & Imagination Technologies
- The role of AI processor architecture in power consumption efficiency
Latest Blogs
- Beyond Trusted: What the NSA’s New Guidance Means for Hardware Security
- A scalable, shader-programmable vector graphics GPU core for low-power MCUs
- Navigating ISO 26262 Part 11: A Guide for Semiconductor Architects
- Embedded Security explained: Digital signatures
- Hardware security verification must go beyond functional testing