Agenda. Convergence One Universal Summary

Size: px

Start display at page:

Download "Agenda. Convergence One Universal Summary"

Hilary Reed
5 years ago
Views:

3 Agenda Convergence One Universal Summary

4 Convergence WHY Mobile OS: WinCE Developer platform:.netcf, Win32CE, OpenGL PC OS: Windows NT Developer platform: Win32,.NET, Silverlight, XNA, DX TV OS (Media Center): Windows NT OS (Xbox): NT-mutant Developer platform Xbox:.NetCF/XNA on Win2K fork Server and cloud OS: Windows NT and Azure

5 Convergence BENEFITS Consistent developer story (internal/external) No porting costs Allow product groups to focus on customer value Increased Agility Innovation and bug fixes flow more rapidly Engineering efficiency Opportunity for improvements/cleanup

6 Convergence OS Products Windows Mobile Windows Clients (Home, Ultimate etc) Windows Servers (Enterprise, Data Center etc) File Serv er DNS / DHC P EV WinPE & Friends Converged OS Mobile Core Client Core Server Core Presentation (DxCore, MFCore, etc) MinServer Core System Mincore PSPs Mincore Minwin PSPs Minwin

7 One WHAT Refactored a common subset of the OS Build all of our products with that common subset on Win10 Properties of this subset: Common codebase Mostly the same binaries (e.g. same kernel) Exposes a subset of the Win32 API surface Kernel mode DDIs are the same as Desktop Common API Surface Universal App Platform (UAP) OneCore Common Driver Surface Universal Driver

8 One WHAT Supports Universal Drivers & Universal Apps Xbox SystemOS Desktop & Server Windows Mobile OneCoreUAPTest OneCoreUAP IoT Athens T 0 Required packages Test packages; ex. VM drivers, tools Optional packages Product specific packages Edition (WIM, VHD, FFU, etc.) Sakura UAP = Universal App Platform

9 One WHAT Product Specific UI (Shell) Out of box experience (OOBE) OneCore-AppRuntime Required by all MSFT OS-es that support universal apps and universal drivers Cortana Compositor Networking Extended IE Core Minuser & win32k Input mgmt. & routing OneCore - Required ETW & Telemetry Kernel XAML CoreCLR WWA DX File System Support HAL OneCore-DeviceRuntime Bluetooth WLAN Low Power Buses Servicing Stack C/C++ Runtime USB Sensors NFC Storage Resource Manager OneCore Optional Packages Usermode Power Infra Core Networking Voice Cellular Stack Mobile Broadband Connection Sharing Network Data Usage Auth Usermode PnP Hyper-V IIS NUI Management COM Crypto Dev. Tools & Transports Cmd.exe Drivers PowerShell T 0 Required packages Microsoft-OneCore-AppRuntime package Test packages; ex. VM drivers, tools Optional packages Product specific packages Edition (WIM, VHD, FFU, etc.)

10 One WHAT Win32 APIs WinRT APIs 1. Universal driver developers 2. System code devs (GPU perf tool) Universal app developers windowsapp.lib onecoreuap.lib WinRT Classes Full Win32 devs kernel32.lib & advapi32.lib Overlappin g API surface

11 Universal WHAT Based on OneCore Kernel/User mode driver Installed as part of a Universal Driver Package.

12 Universal WHAT Runs on all Windows editions that includes the Windows Universal Platform (WUP) Desktop, mobile, IoT All converged device driver stacks are included Value Proposition: Write 1 driver binary per architecture works on desktop, mobile, IoT Single API surface from drivers and apps using WUP Any Windows edition can be used as a driver test platform Sell components to desktop as well as mobile OEMs/ODMS without needing a different driver

13 Universal DO 1. Install Visual Studio 2. Install WDK Includes all headers and libs needed for driver development 3. Select Universal Driver as Target 4. Select architecture (ARM, x86, x64) 5. Add your code, headers, libs, etc 6. Compile / debug / etc. Loop until done 7. Deploy to target machine (dev board) 8. Run available tests

$Universal VALIDATION TOOL Included in the WDK "C:\Program Files (x86)\windows Kits\8.2\bin\x86\apivalidator.$

14 Universal VALIDATION TOOL Included in the WDK "C:\Program Files (x86)\windows Kits\8.2\bin\x86\apivalidator.exe Runs as a post build process for Universal Drivers Also can be run on command line Flags APIs used in the driver project that aren t part of the Windows Universal Platform

15 Universal IMPACT Kernel mode drivers Mostly backwards compatible Minimal changes needed User mode drivers and services Not all Win32 APIs are available as part of Windows Universal Platform A binary (DLL, EXE) linked with missing APIs will not load Replacement APIs may be available in some cases Re-design/re-implementation will be required if APIs are not available

16 Universal PORTING The developer: Developer launches VS and opens existing driver project written for win8 The project get upgraded as part of WDK by default Changes TargetPlatform settings from Desktop to Universal Builds the driver May get build errors because the driver is making calls to APIs not available for universal drivers Remove/replace API calls Builds driver clean, and deploys

17 ONE Summary PC MOBILE TV SERVER/CLOUD U N I V E R S A L

18 (c) 2015 Microsoft Corporation. All rights reserved. This document is provided "as-is." Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. Some information relates to pre-released product which may be substantially modified before it s commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

이창섭부장 IoT Device Experience Microsoft. Windows 10 IoT Technical Overview

이창섭부장 IoT Device Experience Microsoft Windows 10 IoT Technical Overview Windows Devices $ Premium Entry Device Capabilities Windows 10 IoT $ Premium Windows 10 IoT Enterprise Desktop Shell, Win32 apps,