The Evolution of Mobile Technology


Published on

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

The Evolution of Mobile Technology

  1. 1. The Evolution of Mobile Technology Part 4: Breaking Down Challenges in Open Source Tricks of the Trade September 30, 2009 Moderated by Jim McGregor Chief Technology Strategist In-Stat
  2. 2. Introduction  Welcome to the Evolution of Mobile Technology webinar series featuring:  Designing of High-Performance and All-Day Battery life (replay available)  Design Challenges of Supporting Multiple Connectivity Technologies Architectures (replay available)  The Evolution of Mobile Processing Architectures (replay available)  Breaking Down Challenges in Open Source – Tricks of the Trade  The Impact of the Cloud on Mobile Devices (Nov. 3)  The Future of Wireless Technologies (Dec. 8)  Today’s host:  Jim McGregor, Chief Technology Strategist, In-Stat  Agenda:  5-minute overview  30-minute discussion by panelists  25-minute live Q&A  Webinar archive available at:  
  3. 3. Panelists  Jason Kridner  Open platforms principal architect for TI’s application processor group  Defines TI's applications processors strategy for growing the open platform ecosystem of developers and customer base  Designed and drives the development of the BeagleBoard  Eric Thomas  Linux product marketing manager for TI’s wireless group  Identifies, defines, and advocates opportunities to enhance the support of Linux on TI’s application and wireless processors  Defines TI’s activities related to Linux mobile products and the Open Handset Alliance  Represents TI on the board of directors of The Linux Foundation
  4. 4. Overview  Market dynamics (Jim)  Reasons  Limitations  Outlook  Considerations, challenges and tools (Jason/Eric)  What challenges are likely to be encountered  Required tools and support  TI solutions
  5. 5. Why open source?  Potential benefit to OEMs  Low cost  Standardization  Army of engineering resources  Quicker time to market  Change in the software stack  Programmable system designs  Remote and hybrid network applications  3rd party applications
  6. 6. Outlook  Open source is the direction  Transition tied to software stack  Only a few will survive in each segment  Handsets and smartphones moving quickly  Rapidly evolving platforms  Growth of Internet connectivity  Limitation on local resources  Computing moving slowly  Mature platform  Applications slowly moving to the Internet (cloud)
  7. 7. Growing number of open choices Handset / smartphones Network / computing  Chrome OS  Android  Moblin  LiMo  MontaVista  Maemo  Red Hat  Symbian*  SUSE  Ubuntu * Listed as open source but historically a closed OS
  8. 8. In-Stat’s forecast 2009 Smartphone OS Market Share 2014 Smartphone OS Market Share Symbian 25.4% Symbian Other 49.1% 3.0% Windows Mobile Maemo & 9.0% Other Other 2.6% Linux Windows 8.0% Maemo & Mobile RIM Other 9.0% 15.6% Linux 0.2% Apple Apple 19.5% 14.4% Android RIM 20.2% 4.5% Android 19.5% TAM = 153.5 million units TAM = 412.0 million units Source: In-Stat, Sept. 2009
  9. 9. Limitations History Challenges  Consortium creep  Applications  Fragmentation  Battery life  Tools & support  Security  Cost  Standards  Lack of independent  Lifecycle support driver  Quality  Performance  Risk mitigation  Training
  10. 10. Open source: Design considerations, challenges and tools Jason Kridner Open platforms principal architect TI’s application processor group Eric Thomas Linux product marketing manager TI’s wireless group
  11. 11. Open source design considerations  Balancing community benefits  Avoid isolation from the community and integration churn  Focusing on your value add  Avoid starting down a path that won’t meet your needs  Progressive technology baseline  Avoid being obsolete before your time Case study: Android
  12. 12. Alone? Absolutely not.  Give-and-take in community engagement  Goals aligned?  Benefits to progressing community platform?  What is the baseline update frequency?  Update effort = Delta from starting baseline * New baselines  Stable snapshot development  Community synchronized  Increases stability  Increases potential churn  Isolates from community  Leverages the community  High update cost with reduced  Requires defined method for support and external contribution. maintaining value-add update effort update effort
  13. 13. Focus on your value add  Platform with a myriad of options  Ready analog, connectivity, and sensors Supported  Standard expansion busses and drivers Your value add  Open hardware with many implementations  Choose a baseline close to where you add value  Integrated vertical stack or a subset of assembled components?  Avoid futile platform enhancements that reduce ROI Example: Android baseline and integration points  Connectivity, location, motion, orientation, …  Content provider and service interfaces  Distributions, tools, or components on OMAP3  Google, Embinux, 0xLab, Mentor Graphics, Mistral, MOTO, Ingenient, MontaVista, NthCode, MMS, TI, and others
  14. 14. Don’t be ‘out-of-date’ before ‘out-of-gate’  Open source should add value to great technology  Be wary of strong communities supporting aging products  Companies release specifications to minimize ongoing support  Users add enhancements to a commercial consumer product  Replacement for closed source component  Ensure technical specs good before diving into community  Will the supported hardware be sufficient for your market window?  Is the software platform up to date? Vital component: Android’s progressive nature
  15. 15. Progressive nature of OMAP™ platform  Solid foundation for continuing innovation  Latest generation platform to fuel innovation Products Open Development Platforms Zoom-I BeagleBoard Zoom-II OMAP 2 platform OMAP 3 platform OMAP 4 platform  Web browsing and web acceleration capabilities  720p HD video acceleration  8-megapixel camera sensor  WVGA  Expandability, including USB client and Host
  16. 16. Open access to OMAP™ platform resources  Full range of low-cost systems for development and validation  LogicPD’s Zoom™ OMAP34x-II Mobile Development Platform ’s OMAP3530 processor-based USB-powered single board computer  Full documentation at your fingertips  OpenMAX™ IL and OpenGL® ES libraries that enable integration and UI innovation  Free access to DSP acceleration components and compilers  Community collaboration on new solutions enabled by current- generation hardware
  17. 17. Deploying Android on Zoom™ OMAP34x-II MDP 1 Prepare Your Environment Applications • Order Zoom-II MDP using • Configure your Host Linux System Android Platform • Install packages required to build Android 2 OpenMAX IL w/ WLAN, OpenGL ES Get the Sources HW Acceleration Bluetooth • Via public GIT trees at Linux Kernel for Zoom-II MDK AND 3 Building Android • Enable optional features • Multimedia HW Accelerators, WLAN, BT • Build boot loaders, Linux kernel, Android platform 4 Create and Deploy File System • Install system binaries onto SD Card, NFS, or NAND • Boot your system ! Details and Videos at 17
  18. 18. Complete board, complete resources: Zoom™ OMAP34x-II MDP resources Zoom II hardware reference platform Board and project mailing lists Technical reference manuals Active WiKi page: IRC channel: OMAPTM Android project keeping up to date with latest #linux-omap releases from
  19. 19. Complete board, complete resources: BeagleBoard Personally affordable @ $149 Community of >2000 participants Promotes expression of your innovations in wikis, blogs, … Instant access to >10 mil lines of code to start Open hardware and documentation for making your own
  20. 20. Summary  OMAP solutions enable a variety of software platforms  OMAP-based platforms keep up with community to help reduce risks of getting to market  You’re not alone: Robust community surrounding the OMAP platform  Open platforms enable you to focus on value add  Don’t settle for poor technology in search of benefits of open source
  21. 21. Q&A • To participate, click on the Ask a Question link on the left side of the interface; enter your question in the box on the screen; hit “Submit.” We’ll answer them during the Q&A session or after the webcast.
  22. 22. Contact information Jason Kridner Open Platforms Principal Architect, TI’s Application Processor Group Eric Thomas Linux Product Marketing Manager, TI’s Wireless Group Jim McGregor Chief Technology Strategist In-Stat