Guidelines for products that work well with the Microsoft® Windows® xp and Windows Server 2003 operating systems




Download 0.7 Mb.
bet14/22
Sana21.03.2017
Hajmi0.7 Mb.
1   ...   10   11   12   13   14   15   16   17   ...   22

B4.0 Display

B4.1 Display Adapters

B4.1 Display Adapters/Chipsets

All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.

B4.1.1 Display Adapters/Chipsets - Windows Compatibility

B4.1.1.1 "Display and Video Miniport Drivers" and "Multiple Monitor Support in the Display Driver" in the Windows DDK

Software provided with graphics adapters must comply with the requirements defined in "Graphics Driver Design Guide" in the Windows DDK.

Note: This is a general reference, not a requirement.
B4.1.1.2 DELETED
B4.1.1.3 OpenGL support (if implemented): "Video Miniport Drivers" in the Windows DDK

Note: This is a general reference, not a requirement.
B4.1.1.4 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/tech/display/

Note: This is a general reference, not a requirement.
B4.1.1.5 Windows XP: Compatibility Testing Requirements for Display and Video Miniport Drivers

http://www.microsoft.com/hwdev/tech/display/vidminiport.asp
B4.1.1.6 DELETED
B4.1.1.7 DirectX: Support per DirectX DDK and the DirectX SDK

The DirectX DDK is provided in the Windows DDK; the DirectX SDK is provided in the Microsoft Platform SDK at http://msdn.microsoft.com/directx/.

Note: This is a general reference, not a requirement.

Note: If hardware acceleration features are implemented beyond those specified in section B4.1, those features must be supported as defined in the DirectX DDK and SDK.
B4.1.1.8 – See B4.1.4.1
B4.1.1.9 - See B11.1.1.4

B4.1.2 Display Adapters/Chipsets - Industry Standards


Note: This list provides complete titles and web locations for references cited. The listing of a reference here does not imply that complete compliance with that reference is a Windows Logo Program requirement.
B4.1.2.1 Accelerated Graphics Port Interface Specification, Revision 1.0 or later

AGP 2.0: http://developer.intel.com/technology/agp/agp_index.htm.
B4.1.2.2 Digital Video Interface (DVI) Revision 1.0

http://www.ddwg.org/
B4.1.2.3 Display Data Channel Standard, V. 3.0, Level 2B protocols

Video Electronics Standards Association (VESA) BIOS Extension Standard/Core Functions 2.0 (VBE/Core 2.0) at http://www.vesa.org/standards.html
B4.1.2.4 Display Device Class Power Management Specification, V. 2.0

http://www.microsoft.com/hwdev/resources/specs/pmref/PMdisplay.asp
B4.1.2.5 VESA standards for ergonomic timings

VESA Computer Display Monitor Timing Specification Version 1.0, Revision 0.8.
VESA Generalized Timing Formula Standard, Version 1.1.
Or DVI 1.0 (if DVI is implemented).

http://www.vesa.org/standards.html


B4.1.3 Display Adapters/Chipsets - Quality


WHQL Test Specification References:
Chapter 5: Graphics Adapter Test Specification
B4.1.3.1 Pass WHQL tests

See B1.3.

See “Display adapter/chipset” in the HCT documentation.


B4.1.4 Display Adapters/Chipsets - Windows Experience

B4.1.4.1 Multiple monitor/multiple display support
B4.1.4.1.1 Adapter and driver support multiple adapters and multiple monitors

System expansion buses that allow graphics adapters such as PCI and AGP can support the simultaneous use of more than one graphics adapter in the system. Multiple-monitor support can be implemented using add-on PCI graphics adapters. The device drivers for each graphics adapter must provide the required support to allow the presence of multiple adapters and multiple monitors.
B4.1.4.1.2 Onboard graphics device can be used as primary VGA boot device

Mobile PC Note: Systems that have the graphics chip on the system board and mobile PCs that are capable of docking in a docking station with PCI slots must provide a means in the BIOS setup utility to force the system to boot using the onboard graphics device.

This capability is required so the onboard graphics device can be used in a multiple-monitor configuration and for hot undock of a docked mobile system.



For systems with integrated graphics devices that support AGP slot upgrade capability, it is acceptable for the integrated graphics to be disabled automatically. It is not a requirement that integrated devices support multimonitor when an add-on card is installed in the AGP slot.
B4.1.4.1.3 DELETED
B4.1.4.1.4 Requirements for two monitors attached to one display adapter.

For two monitors attached to one display adapter, the following items are required:

  • No additional memory requirements in addition to single-head memory requirements.

  • No AGP GART requirements on secondary head.

  • All minimum single-head requirements must be supported on the primary head, even though resources may vary when dual head is enabled.

  • Required desktop resolution for secondary head is 800 x 600 x 24 bpp.
    Mobile Note: Mobile minimum resolution for secondary head is 640 x 480 with 256 colors. If the secondary head supports Microsoft Direct3D®, it must support 640 x 480 at 16 bpp.

  • Hardware overlay is not required to work simultaneously on both monitors; however, if simultaneous hardware overlay functionality is implemented, both overlays must meet all overlay requirements.

  • 3-D capability is required for the primary head, but isn't required for the secondary head.

  • If 3-D is enabled on the secondary head, it must work, even when dual head is enabled.

  • It is permissible to dynamically change modes; it is not permissible to fail mode changes.

  • Each head must support every mode that is supported when dual head is enabled.

  • The adapter must support enabling both heads simultaneously at 800 x 600 x 24 bpp (minimum required resolution).
    Mobile Note: Both heads support 640 x 480 with 256 colors simultaneously for mobile.

  • If one head is enabled at 800 x 600 x 24 bpp, then the other head must support the maximum resolution reported for that head without failing.
    Mobile Note: This is a maximum resolution of 640 x 480 x 256 colors for mobile chipsets or 640 x 480 x 16 bpp if 3-D is enabled.

  • No dynamic change of Direct3D capability is allowed, regardless of display mode. The primary head's Direct3D capabilities cannot change when the secondary head is enabled.
B4.1.4.1.5 Server system: Requirements for multi-monitor support if capability is implemented

For server systems, the following requirements apply only if the feature is implemented; the inclusion of the related features are not required for display adapters on server systems:

  • B4.1.4.2 Windows XP: Microsoft DirectX® 7 or later driver support for hardware acceleration

  • B4.1.4.5 Color support - (bullet 2) Adapter supports gamma correction performed in hardware at 24 bpp or 32 bpp without using VGA resources

  • B4.1.4.8 Adapter supports hardware-accelerated 3-D graphics
B4.1.4.2 DirectX 7 or later driver support for hardware acceleration
B4.1.4.2.1 Support CopyFourCC

The graphics adapter driver must correctly implement and act on the COPYFOURCC flag as defined by ddCaps.dwCaps2. The blt function is required to take less than 8 ms and must not be emulated in software.

If hardware supports CopyFourCC, it is required that the hardware properly handle Flip Buffers, RGB overlay, nonpower of 2 textures, BLT_FOURCC, YUV textures surfaces, and DirectX VA MPEG acceleration.

This requirement applies now for hardware that supports CopyFourCC.

This requirement does not apply for devices created for 64-bit systems.


B4.1.4.2.2 Properly handle Flip Buffer.

The graphics adapter driver must handle YUV surface flipping properly. Specifically, it must be able to cope with either directed or non-directed flips.
B4.1.4.2.3 Create an RGB overlay as a 3D render target.

If the hardware supports an RGB overlay, then the driver must provide the ability to render 3D content to RGB flipping overlay surfaces. All 3D drawing operations must be complete before the flip causes the surface to be visible on the screen.
B4.1.4.2.4 Support Nonpower of 2 textured surfaces.

If the hardware does not support nonpower of 2 textures, then this must be properly reported by the nonpower2 flag. Because Video sizes are rarely powers of 2, there is an additional DirectDraw® flag called D3DPTEXTURECAPS_NONPOW2CONDITIONAL that should be set if the hardware supports nonpower of 2 textures for the Clamp addressing mode when not using mip mapping and with D3DRS_WRAP(N) set to zero for the texture co-ordinates.
B4.1.4.2.5 Support for BLT_FOURCC.

It is a requirement to be able to simultaneously do a BLT, stretch/shrink, and a color space conversion from a YUV surface to the current 15, 16, 24, or 32 bit desktop RGB formats.
B4.1.4.2.6 If YUV textures are supported, driver can process and function correctly.

If the hardware supports YUV textures surfaces and it is reported as such, then the driver must be able to process these without any intermediate transforms and function correctly.
B4.1.4.2.7 x86-based system: If video decode acceleration is supported by the graphics accelerator, the DirectX Video Acceleration DDI must be supported.

Output of the DirectX VA acceleration process must be available as an input to the VMR renderer. This can either be in the form of a Direct3D texture or as an input to the color conversion BLTer. If video decode acceleration is not present in the hardware, DirectX VA support is not required.
B4.1.4.3 DELETED
B4.1.4.4 Adapter supports minimum screen resolution and timings

Minimum resolution is 1024 × 768 × 32 bpp, double buffered in both 2-D and 3-D modes with a 32-bit Z-buffer in 3-D mode.

Adapter meets VESA specifications for ergonomic timing rates (including, 59.94 Hz variants of the 60 Hz timings); screen resolution and local memory capacity meet minimum requirements.



Mobile PC Note: Requirements are defined in A3.4.4.7

Display adapters often implement more than one display interface (for example, VGA and DVI, VGA and National Television System Committee (NTSC), Dual VGA, DVI and NTSC, and so on). Each interface that is implemented must comply with the appropriate industry specifications for that interface.


B4.1.2.5.1 Analog VGA.

Among other resolutions and refresh rates, the graphics adapter must support the 85 hertz (Hz) ergonomic timings for all required resolutions supported by the monitor up to 1024 × 768. These timings must conform to the Computer Display Monitor Timing Specifications, Version 1, Rev. 0.8, or the VESA Generalized Timing Formula (GTF), Version 1.1. Any higher timings and resolutions must conform to established industry standards. Additionally, in order to provide optimal support for video playback of NTSC broadcasts, the display adapter must support the NTSC (59.94 Hz) refresh rate to assure smooth frame delivery in TV-based video content applications. Phase Alternation Line (PAL) is important in many regions, but there are no specific requirements.
B4.1.2.5.2 DELETED
B4.1.2.5.3 DELETED
B4.1.4.5 Color support
B4.1.4.5.1 Enumeration of supported color depths.

The driver must comply with the following guidelines for enumeration:

  • For 16 bpp, the 5:5:5 mode, the 5:6:5 mode, or both must be supported.

  • If only the 5:5:5 mode is supported, the driver must also enumerate this as 16-bpp mode. This is required because some applications only look for 16-bpp support and will run in 8-bit mode if they fail to find a 16-bit mode.

  • If both 5:5:5 and 5:6:5 modes are supported, both modes must be enumerated.

For each color depth supported, color ordering must be implemented as shown in the following list. Color ordering is shown in the following list from the most significant bit (MSB) to the least significant bit (LSB).

Mode

Color ordering

15 bpp

1 undefined, 5 red, 5 green, 5 blue (URRR RRGG GGGB BBBB)

16 bpp

5 red, 6 green, 5 blue (RRRR RGGG GGGB BBBB)

24 bpp

8 red, 8 green, 8 blue
(RRRR RRRR GGGG GGGG BBBB BBBB)

32 bpp

8 alpha, 8 red, 8 green, 8 blue
(AAAA AAAA RRRR RRRR GGGG GGGG BBBB BBBB)



B4.1.4.5.2 Adapter supports gamma correction performed in hardware at 24 bpp or 32 bpp without using VGA resources.

ICM uses this capability to perform gamma correction for the attached monitor and to allow game applications to switch palettes. This capability also supports transition effects in applications. To provide support for ICM, the graphics adapter gamma must be programmatically adjustable. It is required that downloadable RAM digital-to-analog converter entries be included to perform gamma correction in hardware at 24 bpp or 32 bpp.

This capability must be supported without requiring the use of any VGA resources.


B4.1.4.5.3 Driver supports dynamic color bit-depth change.

The graphics adapter must operate properly and must not fail when asked by the operating system to change the color depth or resolution. A restart must not be required to accomplish this.
B4.1.4.5.4 DELETED
B4.1.4.6 Device configuration and detection requirements
B4.1.4.6.1 DELETED
B4.1.4.6.2 Primary graphics adapter works normally with default VGA mode driver.

Primary graphics adapter works normally with default VGA mode driver

The default VGA driver is required for installing the operating system. The primary adapter must support 4-bit planar VGA mode as described in the Windows DDK.


B4.1.4.6.3Driver does not bypass any Microsoft-provided system components.

This requirement applies for all files normally installed in the System32 directory. These files include, but are not limited to, Win32k.sys, Ntoskrnl.exe, Gdi32.dll, User32.dll, and Mcdsrv32.dll.
B4.1.4.6.4 Adapter supports DDC monitor detection.

And option ROM supports VESA Enhanced Display Data Channel Standard (EDDC), Version 1.0, Level 2B protocols (DDC2B).

The adapter must support the DDC2B host requirements identified in the VESA Enhanced Extended Display Data Channel Standard (E-DDC), Version 1, which defines the communication channel between the display and host system. The software can use this information to properly manage output to the various displays and to prevent the disabling of television output if no monitor is attached. Devices capable of multihead display must support this feature for all attached monitors.



Mobile PC Note: Requirements are defined in A3.4.4.7.
B4.1.4.6.5 Frame buffer can be accessed directly by applications.

Frame buffer can be accessed asynchronously by the CPU and graphics accelerator. It must be possible for applications to perform direct frame buffer accesses at any time, even while asynchronous accelerator operations are being executed.
B4.1.4.6.6 DELETED
B4.1.4.6.7 BIOS supports large frame buffers for graphics adapters.

The system BIOS must support large frame-buffer graphics adapters that have up to 256 MB of frame buffers.
B4.1.4.6.8 Graphics adapter complies with VESA BIOS Extensions/Core 2.0 extensions for power management.

The VESA BIOS Extension Standard/Core Functions 2.0 (VBE/Core 2.0) specification defines extensions to VGA ROM BIOS services for power management.

Note: The required support defined in Version 3.0 of the DDC and Extended Display Identification Data (EDID) standards is also defined in the earlier version and revisions of these standards. As such, the Version 3.0 standards provide the correct references for Windows XP.

Mobile Note: See A3.4.4.7.5
B4.1.4.7 Basic 2-D hardware acceleration requirements
B4.1.4.7.1 Hardware supports transparent blter.

Hardware supports transparent blter. There is no restriction on source size. A transparent blter can perform a block transfer (blt) with a source key transparent color. This requirement assumes that the blter is asynchronous with the host processor.
B4.1.4.7.2 Hardware provides support to prevent tearing.

Hardware provides support to prevent tearing. The hardware must support a mechanism for preventing visible artifacts such as tearing. The mechanism for doing this is at the discretion of the hardware designer, but it must support tear-free capabilities for both full-screen and non-occluded windowed applications. Only one of two simultaneous displays of the same image on two displays (for example, internal mobile panel and external VGA monitor attached) must meet this requirement. The mechanism to prevent tearing must be performed in synchronization with the vertical blanking interval (VBI).

Except when explicitly requested to do otherwise by an application (via Microsoft DirectDraw), blts must synchronize with the vertical scan line to avoid tearing. The ability to read the current scan line supports blting or writing to the screen without tearing. In some contexts, such as video playback, this support eliminates the need for the secondary overlay buffer. Other exceptions to this requirement may be allowed and are documented in the Windows DDK.


B4.1.4.7.3 DELETED
B4.1.4.8 Adapter supports hardware-accelerated 3-D graphics

Including these additional new 3-D requirements for hardware support:
B4.1.4.8.1 Multi-texturing.

Multitexturing hardware can apply multiple textures to a polygon. The most common application of multitexturing is with map-based techniques for diffuse lighting and specular reflections.

Implementing this capability requires supporting two or more sets of independent texture coordinates.

The following texture combination operations are required:


  • MODULATERGB: Component-wise multiplication of both texture colors.

  • MODULATELPHA: Multiply colors of one texture by the alpha of the other.

  • ADD: Component-wise addition of both textures.

  • BLEND: Linear combination of textures weighted by a scalar specified in a register or in a polygon alpha.

Multitexturing is used to compute the texture value that participates in the pixel pipeline implemented in Direct3D.

This technique must work in combination with fogging and alpha blending, but is not required to operate at the same time as other advanced filtering. Multipass multitexturing is acceptable; single-pass multitexturing is preferred.


B4.1.4.8.2 Source and destination alpha blending; required texture size increases to 1024×1024 for all texture operations.

Hardware supports RGB Rasterization. In red-green-blue (RGB) mode under Microsoft Direct3D, shading across a surface is accomplished by independently interpolating all color components. The following capabilities are required for RGB rasterization:

B4.1.4.8.2.1 Textures. These include the following:

B4.1.4.8.2.2 Alpha blending for 3-D graphics. Support for source alpha blending (that is, the blend operation does not require an alpha channel in the render target) and destination alpha blending (that is, the blend operation requires an alpha channel in the render target) is required for all devices. The following table shows the blend modes that must be supported as source and destination factors for alpha blending. All modes must be available in any combination and without dependency on other modes.

Alpha Blending Modes

Blend mode

Source factor

Destination factor

D3DBLEND_BOTHINVSRCALPHA

Required




D3DBLEND_BOTHSRCALPHA

Required




D3DBLEND_DESTALPHA

Required

Required

D3DBLEND_DESTCOLOR

Required




D3DBLEND_INVDESTALPHA

Required

Required

D3DBLEND_INVDESTCOLOR

Required




D3DBLEND_INVSRCALPHA

Required

Required

D3DBLEND_INVSRCCOLOR




Required

D3DBLEND_ONE

Required

Required

D3DBLEND_SRCALPHA

Required

Required

[Deleted]







D3DBLEND_SRCCOLOR




Required

D3DBLEND_ZERO

Required

Required


B4.1.4.8.2.1.3 Lighting and fogging. These requirements include the following:

  • Flat and Gouraud shading (that is, constant and linear interpolation of per-vertex diffuse and specular color attributes). The linear interpolation need not be perspective-correct.

  • Specular highlighting through the addition of an RGB specular color, interpolated from per-vertex specular color attributes. The linear interpolation need not be perspective-correct.

  • Fog effects through blending with an arbitrary RGB fog color. The fog blending term is computed on a per-pixel rather than per-vertex basis, and is range-based (range-based fog) or depth-based (pixel fog). See Windows DDK for definition and discussion of range-based fog and pixel fog.

B4.1.4.8.2.1.4 Driver support for triangle strips and fans. The Direct3D reference rasterizer provided in DirectX supports all of these capabilities.

B4.1.4.8.2.1.5 Hardware complies with texture size limitations. MIP mapping requires that textures of size 1 × 1 be supported. To meet the requirements, a 3-D accelerator must support this lower limit on texture size. The texture units must support square and non-square power-of-two textures (2n × 2m) up to 1024 × 1024 for all texture operations.

Integrated solutions must support destination alpha blending.


B4.1.4.8.3 Texture format 8:8:8:8 alpha RGB (ARGB).

Hardware supports texture formats. Hardware that implements 3D acceleration must support the following 2D, color texture formats:

16 bpp nonpalletized 1:5:5:5 ARGB


16 bpp nonpalletized 4:4:4:4 ARGB
32 bpp nonpalletized 8:8:8:8 ARGB

Integrated solutions must support texture format 8:8:8:8 ARGB.


B4.1.4.8.4 Hardware supports Z comparison modes and Direct3D-compatible formats.

The 3-D hardware must support 32-bit (24-bit Z and 8-bit stencil), unsigned, lockable Z buffer format and all Z comparison modes.

Hardware that supports Z buffering must support clearing of the Z buffer through the DirectDraw depth-fill blt mechanism. In addition, hardware must support clearing of color, Z buffers, and destination surfaces using this method as well.


B4.1.4.8.5 Fog blending term is calculated on a per-pixel basis rather than per vertex.

And is either range-based (range-based fog) or depth-based (pixel fog).
Driver support for triangle strips and fans.

B4.1.4.8.5.1 Integrated solutions must support per-pixel fog.

B4.1.4.8.5.2 Integrated solutions must support MODULATEALPHA texture combinations.

Also, multitexture support with fogging and alpha blending are not required.



Mobile PC Note: Requirements are defined in A3.4.4.7.
B4.1.4.9 Graphics adapter uses PCI, AGP, or another high-speed bus

B4.1.4.9.1 Equivalent of AGP 2X required for discrete solutions; AGP 1X or equivalent required for integrated solutions.

Primary graphics adapter uses AGP or another high-speed connection. AGP requirements are defined in AGP Specification, Revision 2.0. Specific AGP requirements are as follows:



  • Discrete graphics solutions require the equivalent of AGP 2.X.

  • Integrated graphics solutions require the equivalent of AGP 1.X.

  • Other buses, such as PCI, may be used for secondary graphics adapters.
B4.1.4.10 DELETED
B4.1.4.11 Graphics subsystem support for TV or DVD-Video playback, if present, meets performance requirements

If support for TV or DVD-Video playback is implemented, hardware may support video overlay surface with scaling. It is recommended that the overlay surface will be implemented using one of the required YUV formats. If the graphics adapter supports one or more video overlays, the overlay must have the following characteristic:
B4.1.4.11.1 Size.

Discrete Graphics solutions support 720 x 576 or larger surfaces. Mobile platforms and integrated graphics solutions support 720 × 576 or larger.
B4.1.4.11.2 DELETED
B4.1.4.11.3 DELETED
B4.1.4.11.4 DELETED

B4.1.4.11.4.1 DELETED

B4.1.4.11.4.2 DELETED

B4.1.4.11.4.3 DELETED

B4.1.4.11.4.4 DELETED


B4.1.4.12 Graphics adapter driver properly supports D3 state

…such that Windows can hibernate and restore the system from any system-supported sleep state

The Display Device Class Power Management Reference Specification, Version 2.0, provides definitions of the OnNow device power states (D0–D3) for display and graphics devices. The specification also covers device functionality expected in each power state and the possible wakeup event definitions for the class, if any.


B4.1.4.13 – See A3.4.4.7
B4.1.4.14 – See A3.4.4.7
B4.1.4.15 Display Control Panel Extensions per DDK, with Advanced Properties tab

“Control Panel Requirements” Windows DDK

B4.1.5 Display Adapters/Chipsets - FAQs

B4.1.5.1 Current Display FAQs

See http://www.microsoft.com/winlogo/hardware/.
B4.1.5.2 – Updated at B4.1.4.6.8
B4.1.5.3 See A3.4.4.7.5
B4.1.5.4 – DELETED
B4.1.5.5 – DELETED
B4.1.5.6 - Updated at B4.1.4.8
B4.1.5.7 – Updated at B4.1.4.1

B4.1.R Display Adapters/Chipsets - Future Requirements


Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/.
B4.1.R.1 TV output capability, if present, meets requirements
B4.1.4.R.1 Adapter supports underscan scaling.

If TV out is implemented, adapter supports overscan/underscan scaling. The television output adapter must be able to correct horizontal and vertical overscan/underscan using hardware scaling. Software must be able to disable and enable this feature.
B4.1.4.R.2 Adapter supports flicker filter and is required to take a 1024 x 768 32-bpp input and downscale it to TV-out resolution.

If TV out is implemented, the television output adapter must use multiline (three-tap minimum) hardware filtering techniques for flicker reduction. Enable, disable, and adjust capabilities for the flicker filter must be software controllable.

The TV out capability must be able to accept up to a 1024 × 768 progressive desktop and convert it to an interlaced TV resolution output signal.


B4.1.4.R.3 Adapter with TV output supports both 1024 x 768 at 32 bpp VGA and TV output simultaneously.

If TV out is implemented, adapter also supports DVI or VGA and television output. A graphics adapter that supports TV out must also support either DVI or VGA or both. This requirement does not apply to systems with integrated displays. The usefulness of a system is greatly enhanced when any combination of outputs can be active concurrently, but concurrent output support is not required.
B4.1.4.R.4 Software supports positioning.

If TV out is implemented, software must be able to program the television output hardware to position the television image in increments of 4 pixels horizontally and 4 scan lines vertically (or finer). The supported range must be at least /– 40 pixels horizontal and /– 20 scan lines vertical.
B4.1.R.2 Adapter defaults to noninterlaced refresh rate if interlace modes are selected.

Support for interlaced display modes is not required. However, if interlaced modes are implemented and the user selects 1024 × 768 resolution, the graphics adapter must default to a noninterlaced refresh rate with the following exceptions:

  • The attached monitor is not compatible with Display Data Channel (DDC) and the user has not selected a monitor type in the display control panel.

  • The monitor does not support 1024 × 768 non-interlaced mode, as determined from the Extended Display Identification Data (EDID) or monitor registry settings.
B4.1.R.3 Scaling for DTV-enabled PC

For a DTV-enabled PC, the scaling engine must be able to accept an input with a rate of 720p60 (1280 horizontal pixels) and 540p60 (bobbed from 1080i) (1280 horizontal pixels).

B4.2 Monitors


All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.

B4.2.1 Monitors - Windows Compatibility

B4.2.1.1 Monitor INF: "Creating and INF File" in the Windows DDK

See also the “Monitor” sample application in the Windows DDK for information about USB monitor control using Hid.dll.
B4.2.1.2 DELETED
B4.2.1.3 DELETED
B4.2.1.4 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/tech/display/

Note: This is a general reference, not a requirement.
B4.2.1.5 Windows Support for Mobile System Displays

Mobile PC Note: http://www.microsoft.com/hwdev/tech/display/mobiledisplay.asp
B4.2.1.6 – See B4.1.4.15

B4.2.2 Monitors - Industry Standards


Note: This list provides complete titles and web locations for references cited. The listing of a reference here does not imply that complete compliance with that reference is a Windows Logo Program requirement.
B4.2.2.1 Related VESA standards

http://www.vesa.org/standards.html

Enhanced Extended Display Identification Data Standard (E-DID), Release A


DDC2B.
EDID Standard, V. 3.0.
VESA Display Data Channel Standard.
VESA and Industry Standards and Guidelines for Computer Display Monitor Timing.
B4.2.2.2 ICC Profile Format Specification, Spec ICC.1:1988-09 and Addendum 2, ICC.1A:1999-04

http://www.color.org/profiles.html
B4.2.2.3 USB Monitor Control Class Specification, Revision 1.0

http://www.usb.org/developers/docs.html
B4.2.2.4 DVI, Revision 1.0

http://www.ddwg.org/
B4.2.2.5 Display Device Class Power Management Specification, Version 2.0

http://www.microsoft.com/hwdev/resources/specs/pmref/PMdisplay.asp

B4.2.3 Monitors - Quality


WHQL Test Specification References:
Chapter 1: Introduction to HCT Test Specifications
B4.2.3.1 Pass WHQL tests

See B1.3.

See “Monitors” in the HCT documentation.


B4.2.4 Monitors - Windows Experience

B4.2.4.1 Color monitor is DDC2B-compliant and supports EDID 1.3 data structure

A monitor must be compliant with VESA Enhanced Extended Display Data Channel Standard (E-DDC), Version 1, Level 2B protocols (DDC2B), which defines the communications channel between the display and host system. A monitor must assume multiple I2C-compliant devices exist on the communications bus, and as such, a monitor must not impede the use of the I2C bus in any way. A monitor designed for, or included with, a PC 2001 system must not issue DDC1 transactions.

The monitor also must transmit an EDID structure containing unique ID Manufacturer Name and ID Product Code identifiers, plus all required fields, as defined in Section 3 of VESA Enhanced Extended Display Identification Data Standard (E-EDID), Release A.

For analog CRTs, EDID content must indicate at least one VESA mode at 75 Hz, or better, for each resolution supported.

Mobile PC Note
Mobile and other all-in-one systems are not required to support DDC monitor detection. Displays that are attached and connected using an internal interface are not required to provide EDID data identification. This exception applies to all DDC- and EDID-related requirements in this chapter.

All monitors must support E-EDID by implementing an EDID data structure, which includes the following:



  • Set preferred mode bit for all monitor types.

  • Include timing data for the preferred display mode in Timing #1.

For an LCD or other fixed-format display, this would be the native mode of the panel. For other display types, this is the optimal display mode, which is based on the size and capabilities of the device, and must meet the requirements for refresh rates defined in this chapter.

  • Implement monitor descriptors:

Monitor range limits

Monitor name



Note: The required support defined in Version 3.0 of the DDC standards is also defined in the earlier version and revisions of these standards. As such, the Version 3.0 standards provide the correct references for Windows XP.
B4.2.4.2 Monitor associates an ICC profile

Windows supports devices that create standard RGB (sRGB) output by default. Devices with an output other than sRGB must install (via a monitor INF) an ICC profile appropriate to the preferred display resolution (as identified in the EDID data) at 32 bpp. For an LCD or other non-CRT display device, the profile should be based on the native display mode (resolution and color depth) for which the display is designed.

Mobile PC Note: Because most Mobile PCs do not support Plug and Play for their installed LCD panel, the ICC profile must be installed manually by using an appropriate monitor INF. OEMs should install the correct configuration as part of the operating system preinstall process. If necessary, the INF will be available to the user for manual reinstallation. Mobile PCs with Double Supertwisted Nematic (DSTN) or reflective LCD panels do not require ICC profiles.

The ICM APIs and functionality are defined in the Microsoft Platform SDK and the Windows DDK. The requirements for sRGB are defined in IEC 61966-2-1 Multimedia systems and equipment – Colour measurement and management – Part 2-1: Colour management – Default RGB colour space – sRGB, listed in “Monitors References.”


B4.2.4.3 Minimum graphics resolution, based on monitor size

These specific monitor sizes are not required; rather, they show the required pixel format for a given size monitor:

  • 14-inch to 15-inch external monitor = 800 × 600, noninterlaced.

Mobile PC Note: Built-in mobile PC display = 800 × 600, noninterlaced.

  • 17-inch external monitor or 13-inch to 15-inch external LCD = 1024 × 768, noninterlaced.

  • 19-inch and 21-inch external monitor or external LCDs larger than 16 inches = 1280 × 1024, noninterlaced.

  • TV-style large-format monitors (larger than 23 inches) must be capable of scanning at 1024 x 768 progressive at 60 Hz (and 59.94 Hz) for the 4:3 case, and 1280 x 720 progressive at 60 Hz (and 59.94 Hz) for the 16:9 case.

Note: Sizes for LCDs are the actual viewable image size, rounded to nearest inch. Sizes for CRTs are based on actual CRT size (not visible area) rounded to nearest inch.
B4.2.4.4 CRT-based monitor supports ergonomic timing standards

As defined in either the VESA Generalized Timing Formula, V. 1.1 or Computer Display Monitor Timing Specification, V. 1.0, Rev. 0, and a 59.94Hz variant of the 60Hz modes.

The monitor must, at a minimum, support the timings documented in either the VESA Generalized Timing Formula (GTF), Version 1.1 or the Computer Display Monitor Timing Specifications, Version 1, Rev. 0.8. Other resolutions and refresh rates may be supported, but for any resolution less than the required resolution, there must be a timing for 75 Hz or better. The standards help ensure a clear, flicker-free display for traditional PC computing.

To support optimal playback of video content, monitors must be able to operate with the 59.94 variant of the 60 Hz VESA timing. All references to 60 Hz timing in this chapter also include the 59.94 variant.

B4.2.4.5 – See B4.2.4.3
B4.2.4.6 DELETED
B4.2.4.7 USB functionality from either a HID or USB hub, if implemented, is installed separately from the monitor INF
B4.2.4.8 DELETED
B4.2.4.9 CRT-based monitor synchronizes to a new format in less than three seconds

This capability is important because sometimes a change from a high refresh-rate graphics mode to a 60 Hz (or 59.94 Hz variant) mode is necessary to optimize video playback.

When the scanning rate is changed from one of its valid rates to another valid rate, the monitor must resynchronize to the new format and produce a stable picture within three seconds from the graphics adapter becoming stable.


B4.2.4.10 LCD monitor or built-in LCD display contains display characterization data

LCD monitors and built-in displays must be optimized for Microsoft ClearType™ and other advanced operating system graphics features being implemented through DirectDraw, Direct3D, DirectShow, and GDI . This optimization will require additional data regarding the characteristics of the attached display. These characteristics include, but are not limited to:

  • Digital interface (external or internal).

  • Vertical pixel striping orientation in normal orientation (subpixels of the same color aligned in vertical columns).

  • Subpixel format is RGB (ordered left to right). Other formats might be acceptable but must be characterized in EDID.

  • High contrast ratio (minimum of 50:1).

  • No scaling or image filtering applied when display is at native resolution.

  • Detailed gamma data.

  • Additional color information.

  • Monitor rotation capability.

Not all of these characteristics are currently supported in industry standards. These items are noted here for informational purposes and will be documented in appropriate industry specifications and other technical documents as the technologies mature.

The Update on ClearType Font Technology and LCD Displays web page has additional information about ClearType technologies and is listed in “Monitors References.”


B4.2.4.11 Monitor supports 59.94 Hz operation
B4.2.4.12 Monitor complies with Display Device Power Management Reference Specification

Monitors are required to support only D0 and D3 states.

Display Device Class Power Management Reference Specification, Version 2.0 provides definitions of the OnNow device power states (D0–D3) for graphics adapters and monitors. The specification also covers device functionality expected in each power state and the possible wakeup event definitions for the class, if any.


B4.2.5 Monitors - FAQs

B4.2.5.1 Current Monitor FAQs

See http://www.microsoft.com/winlogo/hardware//.
B4.2.5.2 Updated at B4.2.4.1
B4.2.5.3 See B4.2.4.2
B4.2.5.4 Updated at B4.2.4.1
B4.2.5.5 Updated at B4.2.4.12

B4.2.R Monitors - Future Requirements


Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/
B4.2.R.1 Cathode Ray Tube complies with Windows Color Quality Specifications

Color matching capabilities supported in a color cathode ray tube must comply with the requirements defined in Section 4 of "Windows Color Quality Specifications for Cathode Ray Tube OEMs," available at http://www.microsoft.com/hwdev/tech/color/ In particular, the following color tolerances must be met.


Color element

Tolerance

Red primary

x=0.640 0.020/-0.035
y=0.330 0.030/-0.020

Green primary

x=0.300 0.020/-0.035
y=0.600 0.020/-0.020

Blue primary

x=0.150 0.015/-0.015
y=0.060 0.030/-0.015

White point

Where x(sRGB)=0.3127
and y(sRGB)=0.3290
|dx|, |dy| < 0.02
|dx – dy| < 0.02

Luminance(Y)

80 20/-10 cd/m2

Gamma(S-g – simple gamma)

2.2 0.2/-0.2



B4.2.R.2 Liquid Crystal Display (LCD) complies with Windows Color Quality Specifications

Color matching capabilities supported in a color liquid crystal display must comply with the requirements defined in Section 4 of "Windows Color Quality Specifications for Liquid Crystal Display OEMs", available at http://www.microsoft.com/hwdev/tech/color/. Stand alone LCDs are required to use the in gamut patches specified for stand alone LCDs in Section 2 of "Windows Color Quality Specifications for Liquid Crystal Display OEMs." Integrated (laptop) LCDs are required to use the in gamut patches specified for integrated LCDs in Section 2 of "Windows Color Quality Specifications for Liquid Crystal Display OEMs". In particular, the following Delta E tolerances must be met:

Average CIE 1994 Delta E* less than or equal to 10 for in gamut colors.

Maximum CIE 1994 Delta E* less than or equal to 15 for in gamut colors.

Average CIE 1994 Delta E* less than or equal to 20 for IEC 61966-4 colors.


B4.2.R.3 Image Color Management (ICM) APIs and functionality as defined in the Microsoft Platform SDK and "Color Management for Displays" in the Windows DDK
1   ...   10   11   12   13   14   15   16   17   ...   22


Download 0.7 Mb.

Bosh sahifa
Aloqalar

    Bosh sahifa


Guidelines for products that work well with the Microsoft® Windows® xp and Windows Server 2003 operating systems

Download 0.7 Mb.