Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
History Lesson
The Vision
The Process of Evolution
Dogfooding
The Key to Implementation
3
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
CE2.0 CE3.0 WM5 WM7
ODOCEPC
GE BSP Pack w/
13 platforms
1Build the 1st BSPs
Microsoft ships it’s first
WM BSPOne SV has a
PPC BSP
Microsoft ships 2 LTK compliant
WM BSPs
Majority of Phone CPUs have WM BSPs with the
others knocking on the door
2Creation of
Production Quality
3Enable a self-
sustaining Market
>
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
“Survey says…” Our BSP Architecture is valuable
100% useful or better = it’s easily portable to enable TTM
Results prove that the 2nd Evolution (Production Quality) has in fact happened
PQ – BSPs are now available
Critical
60%High Impact
20%
Useful but
not critical
20%
0% of low
impact
reference
only
% Reuse of Microsoft Architected
BSP code on OEM's Product
Development Cycle
Data from 10 OEMS
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
We’ve crossed another major inflection pointOperators and OEMs are demanding Windows Mobile
AND
OxMs have a choice in the chips they use in WM
These two enable competition in the chipset selection for WM OxMs
The competition drives the SV to build a better BSP then their competitors as well as a better chip
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
“OEMs and Silicon vendors are able to ship innovative devices that are great platforms for Windows Mobile apps and services, with minimal effort and minimal direct support from Microsoft”
Key Take-away: OEM gets their BSP from Silicon Vendor
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
Mission Statement: We work on advancing BSP’sImplement new bootloader, kitl, oal and driver technologies
Define the feature set of a rich BSP
• Define the quality bar and continuously raise it• Write the tests that measure
Functionality
Stability
Performance
Silicon Vendors ship their own BSPsMicrosoft still assists in development of new technologies
Continue work on strategic BSPs in house and use them where necessary for OS validation
We live our process with the devices we use every day
We hold ourselves to this bar and raise it with every release
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
Chip1 Chip2
Chip3
Chip4 Chip5
Chip N
Usb 2.0 HS x Arch. x
Graphics accelerator
Arch. X x x
Bluetooth 2.0 Arch. MSFT
3G Arch. X X
Serial GC
IrDA GC
This is a strategic investment so we dive deep with the SV
Arch. = Architect does this work. Could be Microsoft could be SVGC = General contractor. Could be SV or could be paid for Systems Integrator
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
Drop1 Drop2 Drop3
Build a BSP Technology Pack on JetStream
Chip 1
Chip 2
Chip 3
JetStream
Micro
soft S
hip
sSilico
n V
en
do
r Sh
ips
USB KITL OAL SDIO
USB KITL OAL SDIO
USB KITL OAL SDIO
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
Everyone can come play in the WM yard as long as they are playing our quality game
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
BSP Test Suite
What is a High Quality BSP
Silicon Vendor
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
None of this is possible if we don’t have the tools that enable SVs to do the work themselves. There must be a clear and consistent bar for everyone
BSP Test Suite – a BSP score based on:Features and Functionality
Performance and Stability
Standardize Security and PQD
process to validate code architecture
BSP Bin – the functional definition for a BSP. It identifies all the attributes of the bootloader, OAL and all drivers
Big Book of BSPs – this is a focused set of living documentation, published on a wiki, that steps a BSP developer through his tasks
Reinstitute WM BSP Tech Fests – use this as a stage to deliver Engineering Excellence methodology and our Architectures
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
LTK:Brand protectionOxM must run
BTS:BSP QualitySV must run, OxM consumes results
CETK:Individual Driver testsAnyone can use
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
New requirements Quality Enhancements
Definition of a BSP and it’s quality
Strategic
BSP and Dogfood
BSP Test SuiteBSP Bin
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
We work with SV on their BSP with rights to some of the source code
SV gives that BSP to OEM with rights to redistribute parts back to Microsoft
We license that code back for Dogfood. We can work on Dogfood that we helped build the BSP for
We apply this commercialization learning to the next platform
“The Continuum”
Silicon Vendor
OEM
Microsoft Dogfood
Microsoft Strategic
investment
Windows Mobile “7”
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Windows Mobile “7” Microsoft Confidential. For discussion purposes only.
©2007 Microsoft Corporation. All rights reserved. Microsoft, Dynamics, Exchange, Expression, Internet Explorer, Live, MSN, .NET Compact Framework, Office Online, Office Communicator, Outlook, System Center, Silverlight, SQL Server Compact Edition, Visual Studio, Windows Live Hotmail, Windows Mobile
Available programs, features, and functionality vary by device, Windows Mobile operating system version, and version of Exchange server used. Connectivity and synchronization may require separately purchased equipment and/or wireless products (e.g., WiFi card, network software, server hardware, and/or redirector software). Service plans are required for Internet, WiFi and phone access. Features and performance may vary by service provider and are subject to network limitations. See device manufacturer, service provider and/or corporate IT department for details.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date