USB 2.0 Software Roadmap Update

1
(No Transcript)
2
USB 2.0 Software Roadmap Update

• Robert Ingman
• Program Manager LeadWindows Division
• Microsoft Corp.

3
Microsoft USB 2.0 Update

• Software roadmap update
• What?
• When?
• Why?
• Software architecture update
• How?

4
Roadmap Agenda

• Industry plan
• Microsoft plan
• Microsofts ship criteria
• Early adopter plan
• Current status
• USB 2.0 and storage devices
• Call to action

5
USB 2.0 Industry Plan

• Enable better end user experience
• Enable early adopter OEMs to sell PCswith USB
  2.0 in Q4 2000
• Discrete host controller implementations
• PCI add-in cards as OEM configuration option
  first, then on motherboards as well
• Hubs and limited set of peripherals
• Broad availability by mid-2001
• Host controllers integrated into chipsets
• Retail PCI add-in cards available
• Full range of high-speed peripherals available

6
USB 2.0 Microsoft Plan

• Tentative early adopter USB 2.0 driver support
  for Windows 2000 in Q4 2000
• Only if hardware is ready in time
• Tentative full USB 2.0 support in Windows
  Whistler releases in 2001 for consumer,
  workstation, and server markets
• Tentative back-ports of USB 2.0 driver
  supportfor Windows ME and Windows 98 SE by
  mid-2001
• No driver support for Windows 98 gold

7
Why Windows 2000 First?

• Windows 2000 is our USB 2.0 development platform
• We develop and test on Windows 2000 first anyway
• Reduces risk
• Reduces test burden
• Windows 2000 is now Microsofts strategic
  foundation for all future OS efforts
• Paves the way for USB 2.0 support in Windows
  Whistler and beyond
• Enables early focus on business customers and
  prosumers

8
Microsofts Ship Criteria

• Before Microsoft USB 2.0 driver stack ships, for
  any Windows OS, we need at least 3 months of
  solid end-to-end testing with the following
  hardware
• Production-quality USB 2.0 host controllers
  fromat least 2 vendors
• Production-quality USB 2.0 hubs from at least3
  vendors
• Production-quality USB 2.0 peripherals fromat
  least 6 vendors

9
Early Adopter Plan

• Early adopter OEMs and IHVs should plan to
  spend time resources at Microsoft this summer
• 3-month test pass for Windows 2000 currently
  planned for July September
• Microsoft is prepared for some flexibility in
  hardware schedules, but that in turn requires
  hardware partners to be flexible w/ regards to
  final driver release date
• USB 2.0 host controllers, hubs, and peripherals
  as specified by our ship criteria need to be part
  of theentire test pass

10
Early Adopter Test Flow

• First at Intel for hardware debugging
• Low-level electrical work
• Bus signaling work
• Any work that requires extensive use of scopes,
  etc
• Compliance and interop testing
• Then at Microsoft when you are ready to
• Have your device enumerated by a 2.0 host
  controller
• Have Windows load a driver for it

11
Current Status
As of May 8, 2000

• New USB 2.0 driver stack up running
• New port driver
• New mini-port drivers for EHCI and OHCI
• Early testing of driver stack with
• 2 eval EHCI host controllers
• First eval peripherals just showing up
• Scanners, storage devices
• USB 2.0 hubs not part of the mix yet
• Hardware not yet available
• Test tools being developed in parallel

12
USB 2.0 Support in 2000

• Target OS Windows 2000
• Hardware availability is the critical path
• Will there be enough production-quality
  hardwarefor Microsoft to test with?
• We are especially worried about 2.0 hubs
• The schedule is very aggressive
• We need to work very closely, on a daily and
  weekly basis, with our early adopter hardware
  partners in order to succeed

13
USB 2.0 and Storage Devices

• USB 2.0 is fine for secondary add-on storage
• Microsoft has no plans in place currently to
  support a USB 2.0 storage device as the primary,
  bootable device
• This means no support for system boot partitions,
  paging, hibernation, or crash-dumps
• Recovery boot from USB 2.0 CD-ROM drive will be
  supported, but requires specific BIOS support as
  well (El Torito specification)

14
Call to Action

• Early adopter USB 2.0 driver support for
  Windows 2000 in Q4 2000 is gated on hardware
  availability
• CONTACT US NOW if you are ready to participate in
  this effort
• NOTE your hardware needs to be ready for heavy
  duty testing in Microsoft labs during July
  September
• New USB 2.0 hardware is always welcome at
  anytime, of course
• Contact us at MSUSB2_at_MICROSOFT.COM

15
USB 2.0 Software Architecture Update

• Kenneth Ray
• Development Lead Windows Division
• Microsoft Corp.

16
Architecture Agenda

• USB 2.0 architecture overview
• Driver changes by bus transfer type
• Early adopter plan
• Implementation risks
• Summary of USB 2.0 work
• Selective Suspend
• Conclusion

17
USB 2.0 Architecture Overview
New drivers

Updated drivers
18
Driver Changes byBus Transfer Type

• Amount of changes (and risk) variesby device
  type
• LOW Low-Speed (LS) and Full-Speed (FS)devices
  through USB 2.0 hub
• MEDIUM High-Speed (HS) Bulk / Interrupt devices
• HIGH High-Speed (HS) Isochronous devices

19
LS and FS Devices
Bulk, Interrupt, Isochronous

• Enabled through a USB 2.0 hub
• No changes to USBD interface required
• Client drivers and apps are unaffected
  (transparent)
• Little to no changes required in MS Hub driver
• Transaction Translator support built into USB
  mini-port driver (based on endpoint type)

20
HS Bulk and Interrupt

• No changes to USBD interface required
• Client drivers and apps are unaffected(just
  higher speeds)
• For example, the USB mass storage class driverin
  Windows 2000 does not need to be changed

21
HS Isochronous

• Extensions required to USBD interface
• New support for micro-frames
• 8 packets per ms instead of 1 per ms
• New data structure to define transfer
• Client drivers and apps are affected and
  willneed to change
• Audio/DirectSound, video capture, kernel
  streaming, DirectShow, etc
• Microsoft client driver support for HS
  Isochronous will therefore first be released in
  new OS, and might not be back-ported

22
Early Adopter Plan

• Requires hardware to show up on time!
• LS / FS Bulk and Interrupt OK
• FS Isochronous via 2.0 hub OK
• HS Bulk, Interrupt OK
• HS Isochronous
• New USBD interface prevents existing MS client
  drivers and apps from taking advantage of it
• New USBD interface will be exposed if we have
  enough devices to test it with then 3rd-party
  drivers could take advantage of it

23
Implementation Risks

• Low for LS and FS devices through a 2.0 hub
• Based on hub
• Lots of LS and FS devices available
• Higher for HS Bulk
• LS and FS testing through hub also exercisesthis
  code path
• We need lots of HS Bulk devices to test with!
• Will anyone build HS Interrupt devices?

24
Implementation Risks
Continued

• Highest for HS Isochronous
• FS testing through hub exercises only
  someinternal code paths
• We need some HS Isochronous devices to test with!

25
New UI for USB 2.0

• Microsoft will extend current Device Manager
  UIto cover USB 2.0 HCs and hubs as well
• Bandwidth and Power property pages
• Additional topology error pop-up UI to cover
  new scenarios
• 2.0 device plugged into 1.0 port on 2.0-capable
  system user needs to be guided to plug in device
  into 2.0-capable port instead, etc
• Enumeration errors, etc

26
Summary of USB 2.0 Work

• Transaction Translator support is built into new
  USB mini-port driver
• LS and FS Bulk, Interrupt, and Isochronous
• No changes to client drivers, apps, or USBD, and
  few(if any) changes to Hub driver
• HS Bulk
• No changes to client drivers, apps, or USBD
• HS Isochronous
• Requires changes to client drivers (audio, video
  capture, etc)
• Extensions to USBD to support micro-frames

27
Selective Suspend

• Allows individual devices to be selectively
  suspended (D2) when idle even when system itself
  is fully awake (S0)
• Allows root ports to be suspended if all USB
  devices are idle, and the HC can be put into a
  low-power state (C3)
• Will result in battery power savings for mobile
  systems
• Scheme is cooperative, and requires that all
  devices drivers go into idle state when
  inactive
• Client drivers must be able to put devices into a
  low-power state even when system itself is awake
• Microsoft will initially rev HID and
  keyboard/mouse drivers to take advantage of this
  new feature

28
Selective Suspend
Continued

• Power down
• New IOCTL in USBHUB that client driver calls
  whendevice is idle
• Callback routine tells client driver to power
  down deviceusing standard PoXxx call
• NOTE client driver must post WAIT_WAKE IRP for
  wake-up capable device before powering down
  device
• Power up
• Wake-up capable device generates standard resume
  signaling when activated by the user, WAIT_WAKE
  IRP gets completed, and client driver issues
  Set_D0 request to device, OR
• Client driver issues Set_D0 request to device in
  response to host software activation

29
Conclusion

• USB 2.0 driver development work leverages what
  was done for USB 1.0
• Scope of work is doable for end-of-year 2000
  products
• Re-use of USB1.x driver code reduces risk
• Microsofts USB team is staffed and fully
  committed to USB 2.0
• Microsofts ability to support USB 2.0 early
  adopters is gated on the early availability of
  enough host controllers, hubs, and peripherals

30
Questions?