Transcript Auxiliary Display Platform in Longhorn Andrew Fuller Lead Program Manager Mobile PC afuller @ microsoft.com Microsoft Corporation.

Auxiliary Display Platform in Longhorn
Andrew Fuller
Lead Program Manager
Mobile PC
afuller @ microsoft.com
Microsoft Corporation
Session Outline
Introduce auxiliary displays
Software platform
Hardware platform
Hardware examples
Laptop in-lid
Laptop edge/keyboard display
Front panel display
Network attached displays
Q&A
Session Goals
Introduce the new auxiliary display platform for
Windows codenamed “Longhorn”
Describe software platform and ISV extensibility
Show hardware options for differentiation
Give examples of hardware implementations on
different form factors
What is an Auxiliary Display?
Choice 1
A small display embedded
in a PC that can show
limited amounts of data and
be powered independently
from the main system
Choice 2
A device that is capable of
connecting to a PC and can
display information
What are Auxiliary Displays Used For?
Showing information quickly from
the PC such as
PC Status information (e.g. wireless strength)
Notifications (e.g. battery low)
Application specific data (e.g. next meeting)
Why?
Makes the PC more useful in more settings
Makes the mobile PC more available for more
of the day
Extends the PC experience to more devices
Longhorn Software Platform
New for Longhorn
New APIs for ISVs
Supports different device capabilities (e.g. color)
Scales to multiple devices
Control Panel for users to control applications
and configure display setting
Architectural Overview
Uses Windows Portable Devices infrastructure
Easy way to talk to range of devices including cell phones
Allows for IHV extensibility via user mode driver model
Aux displays will appear in device manager; integrated with
Function Discovery
Content format supports 3 basic primitives
Menu
Dialog
Content page (text & graphics)
Navigation events are passed back to ISV application
Geared towards providing simple user interaction across
multiple devices with varying capabilities
XML-based
Data Modes
Full interaction
Navigate between applications
Navigate between pages of data in an app
(e.g. reading email)
Events passed back to PC for processing (e.g. next
slide in PPT, next track in WMP)
Glance mode
Apps can supply top-level info (e.g. “5 unread emails”,
“Next meeting in 15 mins”, “Seattle 63F”)
Notifications
Windows generated alerts (e.g. battery low, IM sign-in)
ISV generated alerts (e.g. news headline, sports results)
Enhanced Display Architecture
ISV Client Application
Auxiliary Display Client API layer
WPD API layer
Windows User-mode Driver Framework
WPD
Enhanced Auxiliary
Display Driver
TinyCLR communication driver
Windows USB Driver
Hardware Options
Two main hardware options:
Enhanced display
Uses Microsoft provided driver
Runs Microsoft developed firmware
Supports full interaction, glance mode and notifications
Basic display
Requires driver to interface to auxiliary display platform
Firmware developed by hardware partner
Data support selected by hardware partner
Enhanced Display
Rich UI and interaction
Caches data for use in S3-S5
Microsoft providing:
Device runtime (TinyCLR)
Hardware concept design
Full driver stack – USB
Longhorn look-and-feel user experience
Hardware Concept Design
Refining design
Current guidelines are:
ARM7 or ARM9 processor (approx 75Mhz)
Flash: minimum 2MB (more for Asian languages)
RAM: minimum 4MB
USB: 1.1 minimum
I2C connection for SMBus command-and-control and
battery status
Separate connection to battery
TinyCLR as device runtime
Approx 350KB
Currently available on ARM7 & ARM9
Enhanced Display Hardware Concept Design
Cache
Memory
Host PC SMBus
Host PC USB Hub
I2C
Controller
ARM7
Processor
USB 1.1
Controller
Display
Controller
Display Panel
Enhanced Display Extensibility
IHV can extend device to support new hardware
IHV/OEM visual presence
Watermark/background image
Custom on-device applications
Dedicated space in UI for additional icons
Non-extensible areas
Support fixed number of display controllers
and display resolutions
Minimum set of buttons
Initially restricted to ARM chipsets
Basic Displays
Built on WPD
Additional auxiliary display DDI
Two options:
IHV can write to auxiliary display DDI and convert content format
into device specific format
IHV can use MTP class driver and interpret Simple Content
Format in device firmware
Connection agnostic with appropriate protocol driver
(e.g. USB, UWB, Bluetooth)
Level of content support defined by hardware partner
For example: could choose to only support notifications
Requires firmware from hardware partner
Basic Display Architecture
ISV Client Application
Auxiliary Display Client API layer
WPD API layer
Windows User-mode Driver Framework
WPD
Basic Auxiliary Display
Driver
IHV specific content driver (e.g. bitmap or GSM-AT)
IHV protocol driver (e.g. USB, Bluetooth)
Hardware Examples
Laptop in-lid
Laptop edge/keyboard display
Front-panel
Smart alarm clock
Cell phone
Laptop in-Lid Display
Scenarios
Interactive data
Browse calendar, browse email
Control media playback
Glanceable data & notifications
Technology
Enhanced display architecture
ARM processor, memory
Separate power connection
SMBus connection for waking PC
USB connection to PC for data
Laptop Edge/Keyboard Display
Scenario
View user configurable alerts and top level info
(e.g. media ‘now playing’, news headlines,
IM sign-in)
Limited or no user interaction
Technology
Glance mode & notifications
Basic display architecture
USB or Bluetooth connection to PC
Laptop Edge Display Examples
Small Business Server Front Panel Display
Scenario
View server status information
User selectable boot options
Configure and manage server storage and networking
options
View error diagnostics
Technology
Enhanced or basic display architecture (depending on
UI and level of interaction)
Direct connection to power source
SMBus for command-and-control
USB connection to Server for data
Smart Alarm Clock
Scenario
Automatically set alarm based on first meeting
View weather and traffic reports
Technology
Enhanced or basic display architecture (depending on
UI and level of interaction)
802.11 connection to PC
Uses Web Services for Devices (WSD) for network
discovery – enumerated as a PnPx WPD device
Cell Phone
Scenario
Remote control for media players and PowerPoint
View notifications from the PC (e.g. in range of
wireless hotspot)
Technology
Basic display architecture using MTP driver
MTP compatible firmware required on cell phone
Connection via Bluetooth
Timeline
Beta 1 plan
Core platform: enhanced display only
SDK: with software simulator and sample apps
HDK: with enhanced display concept
hardware design
Contact mobaux @ microsoft.com for the HDK
Beta 2 plan
Auxiliary Display Control Panel
Basic display support
Platform enhancements
Call to Action
Include an auxiliary display as part of your PC
designs
Add auxiliary display functionality to new or
existing devices
Evangelize auxiliary display platform
to ISV partners
Community Resources
Windows Hardware & Driver Central (WHDC)
www.microsoft.com/whdc/default.mspx
Technical Communities
www.microsoft.com/communities/products/default.mspx
Non-Microsoft Community Sites
www.microsoft.com/communities/related/default.mspx
Microsoft Public Newsgroups
www.microsoft.com/communities/newsgroups
Technical Chats and Webcasts
www.microsoft.com/communities/chats/default.mspx
www.microsoft.com/webcasts
Microsoft Blogs
www.microsoft.com/communities/blogs
Additional Resources
Email: mobaux @ microsoft.com
Related Sessions
TWDT05007 Mobile PC Extensibility
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.