q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
GREENWOOD / BLACK WALL STREET WILMINGTON 1898 LITTLE ROCK NINE TUSKEGEE STUDY ROSEWOOD 1923 THE TUSKEGEE AIRMEN SENECA VILLAGE BLACK TOWNS GREENWOOD / BLACK WALL STREET WILMINGTON 1898 LITTLE ROCK NINE TUSKEGEE STUDY ROSEWOOD 1923 THE TUSKEGEE AIRMEN SENECA VILLAGE BLACK TOWNS
What's New!
THE JOURNEY THROUGH TIME
BHP HOME BEFORE AMERICA 1800–1936 1937–1957 1958–1980 1981–2000 2001–PRESENT

Explore Black History

Explore the people, places, events, achievements, struggles and stories that shaped our journey.

✊🏾

Civil Rights

Movements, leaders, victories and the continuing fight for equality.

⚙️

Black Inventors

Innovation, patents, science, technology and world-changing contributions.

🏆

Sports

Pioneers, champions, Negro Leagues, records, activism and excellence.

♟️

People

Meet the people whose lives, choices and achievements shaped the journey.

📍

Places

Black towns, communities, institutions and places where history happened.

📜

Events

Moments that changed communities, movements, institutions and the nation.

Enter a person, place, event, or topic.
MY'STORY

The MOVE Fire

This is a personal recollection on the Move fire on May 13, 1985 Philadelphia police fired thousands of rounds at the MOVE house, city officials approved dropping an explosive device on the roof, the resulting fire was allowed to burn, 11 people—including five children—died, and 61 homes were destroyed. Philadelphia City Council later called it a “brutal attack carried out by the City of Philadelphia on its own citizens” and acknowledged that no individual faced criminal consequences for the bombing. One timeline correction worth preserving for the BHP record: the major previous MOVE-police confrontation was August 8, 1978, about seven years before the bombing, not a year or two earlier. Officer James Ramp was killed, other police and firefighters were wounded, nine MOVE members were later convicted, and television cameras recorded police beating Delbert Africa during his arrest. The 1985 MOVE Commission later specifically criticized city planners for failing to adequately use lessons from that 1978 confrontation. And that actually strengthens the point you’re making: 1985 did not happen without precedent or institutional memory. There had already been a deadly confrontation with MOVE, years of conflict, negotiations and police involvement before Osage Avenue.

MORE →
BLACK FACTS
The Truths They Never Taught You...

Shirley Chisholm — Unbought and Unbossed

In 1968 Shirley Chisholm became the first Black woman elected to the United States Congress. In 1972 she launched a campaign for the Democratic presidential nomination, breaking another political barrier.

MORE →
BHP gathered finds from its connected research sources. Showing the 4 strongest Black History matches.
← BACK TO RESULTS
Wikipedia

Windows Display Driver Model

Windows Display Driver Model (WDDM,[1] initially LDDM as Longhorn Display Driver Model and then WVDDM in times of Windows Vista) is the graphic driver architecture for video card drivers running Microsoft Windows versions beginning with Windows Vista.[2]

It is a replacement for the previous display driver model of Windows 2000 (called XDDM) and Windows XP (called XPDM)[3] and is aimed at enabling better performance graphics and new graphics functionality and stability.[2] Display drivers in Windows Vista and Windows 7 can choose to either adhere to WDDM or to XDDM.[4] With the removal of XDDM from Windows 8, however, WDDM became the unified option.[5] In Windows 2000 and Windows XP, the XDDM/XPDM is based on WDM.

WDDM provides the functionality required to render the desktop and applications using Desktop Window Manager, a compositing window manager running on top of Direct3D. It also supports new DXGI interfaces required for basic device management and creation. The WDDM specification requires at least Direct3D 9-capable video card and the display driver must implement the device driver interfaces for the Direct3D 9Ex runtime in order to run legacy Direct3D applications; it may optionally implement runtime interfaces for Direct3D 10 and higher.

Features enabled by the WDDM

[edit]

WDDM drivers enable areas of functionality which were not uniformly provided by earlier display driver models. These include:

Virtualized video memory

[edit]

In the context of graphics, virtualization means that individual processes (in user mode) cannot see the memory of adjacent processes even by means of insertion of forged commands in the command stream. WDDM drivers allow video memory to be virtualized,[6] and video data to be paged out of video memory into system RAM or into page file. In case the video memory available turns out to be insufficient to store all the video data and textures, currently unused data is moved out to system RAM or to the disk. When the swapped out data is needed, it is fetched back. Virtualization could be supported on previous driver models (such as the XP Driver Model) to some extent, but was the responsibility of the driver, instead of being handled at the runtime level.

Scheduling

[edit]

The runtime handles scheduling of concurrent graphics contexts.[7] Each list of commands is put in a queue for execution by the GPU, and it can be preempted by the runtime if a more critical task arrives and if it has not begun execution. This differs from native threads on the CPU where one task cannot be interrupted and therefore can take longer than necessary and make the computer appear less responsive. A hybrid scheduling algorithm between native and light threads with cooperation between the threads would achieve seamless parallelism. Scheduling is not a new concept, but it was previously the responsibility of individual driver developers. WDDM attempts to unify the experience across different vendors by controlling the execution of GPU tasks.

Cross-process sharing of Direct3D surfaces

[edit]

A Direct3D graphics surface is the memory area that contains information about the textured meshes used for rendering a 2D or 3D scene. WDDM allows Direct3D surfaces to be shared across processes.[8] Thus, an application can incorporate a mesh created by another application into the scene it is rendering. Sharing textures between processes before WDDM was difficult, as it would have required copying the data from video memory to system memory and then back to video memory for the new device.

Enhanced fault-tolerance

[edit]
Windows Vista alerting the user of a successful WDDM recovery
Windows XP alerting the user of a successful recovery from a XPDM crash to a fail-safe mode

If a WDDM driver hangs or encounters a fault, the graphics stack will restart the driver.[2][9] A graphics hardware fault will be intercepted and if necessary the driver will be reset.

Drivers under Windows XP were free to deal with hardware faults as they saw fit either by reporting it to the user or by attempting to recover silently. In some cases when the display driver can be safely stopped, Windows XP may instead alert about the display driver crash, while also disabling the video driver, thus switching down the screen resolution to 640x480 with only 16 colors. With a WDDM driver, the screen resolution will most likely be unaffected; all hardware faults cause the driver to be reset and the user will be notified by a popup; this unifies the behavior across vendors.

Previous drivers were fully implemented in kernel mode, whereas WDDM is implemented partly in user mode. If the user mode area fails with an unrecoverable error, it will, at the most, cause the application to quit unexpectedly instead of producing a blue screen error as it would in previous driver models.

WDDM also allows the graphics hardware to be reset and users to update drivers without requiring a reboot.[2]

Limitations

[edit]

The new driver model requires the graphics hardware to have Shader Model 2.0 support at least, since the fixed function pipeline is now translated to 2.0 shaders. However, according to Microsoft as of 2009, only about 1–2 percent of the hardware running Windows Vista used the XDDM,[10] with the rest already WDDM capable. It also requires some other hardware features; consequently some SM 2.0-supporting hardware such as the Intel GMA 900 fails the WDDM certification.[11]

One of the limitations of WDDM driver model version 1.0 is that it does not support multiple drivers in a multi-adapter, multi-monitor setup. If a multi-monitor system has more than one graphics adapter powering the monitors, both the adaptors must use the same WDDM driver. If more than one driver is used, Windows will disable one of them.[12] This is a limitation from when Windows Vista was codenamed Windows "Longhorn".[13] WDDM 1.1 does not have this limitation.[14]

WDDM 1.0/1.1 does not allow some modes that were previously handled by the driver such as spanning mode (stretching the desktop across two monitors)[15][16] although Dual View is still available.[12][17]

Need for a new display driver model

[edit]

One of the chief scenarios that the Windows Display Driver Model enables is the Desktop Window Manager. Since the desktop and application windows managed by DWM are Direct3D applications, the number of open windows directly affects the amount of video memory required. Because there is no limit on the number of open windows, the video memory available may prove insufficient, necessitating virtualization. As the window contents that DWM composes into the final desktop are generated by different processes, cross-process surface sharing is necessary. Also, because there can be other DirectX applications running alongside DWM on the DWM-managed desktop, they must be able to access the GPU in a shared manner, necessitating scheduling.

Though this is true for Microsoft's implementation of a composited desktop under Windows Vista, on the other hand, a composited desktop need not theoretically require a new display driver model to work as expected. Successful implementations of composited desktops were done before Windows Vista on other platforms such as Quartz, Compiz, WindowFX. The approach that Microsoft attempted was to try to make sure WDDM was a unified experience across different GPUs from multiple vendors by standardizing their features and performance. The software features missing from other driver models could be made immaterial by extensions or if a less restrictive or simply different driver model were in place.

History

[edit]

WDDM 1.0

[edit]

Windows Vista introduced WDDM 1.0 as a new display driver architecture designed to be better performing, more reliable, and support new technologies including HDCP. Hybrid Sleep, which combines hibernation and sleep mode functionality for enhanced stability in the event of power failure, also requires WDDM.[2][why?]

WDDM 1.1

[edit]

Windows 7 supports major additions to WDDM known as WDDM 1.1; the details of this new version were unveiled at WinHEC 2008. New features include:[10]

Hardware acceleration of GDI and Direct2D/DirectWrite operations helps reduce memory footprint in Windows 7, because DWM compositing engine no longer needs to keep a system memory copy of all surfaces used by GDI/GDI+, as in Windows Vista.[23][24][25]

DXGI 1.1, Direct3D 11, Direct2D, and DirectWrite were made available with Windows Vista Platform Update; however GDI/GDI+ in Vista continues to rely on software rendering[26] and the Desktop Window Manager continues to use Direct3D 9Ex.[27]

WDDM 1.1 drivers are backward compatible with WDDM 1.0 specification; both 1.0 and 1.1 drivers can be used in Windows Vista with or without the Platform Update.[10]

WDDM 1.2

[edit]

Windows 8 includes WDDM 1.2[28][29] and DXGI 1.2.[29][30] New features were first previewed at the Build 2011 conference and include performance improvements as well as support for stereoscopic 3D rendering and video playback.

Other major features include preemptive multitasking of the GPU with finer granularity (DMA buffer, primitive, triangle, pixel, or instruction-level),[31] reduced memory footprint, improved resource sharing, and faster timeout detection and recovery. 16-bit color surface formats (565, 5551, 4444) are mandatory in Windows 8, and Direct3D 11 Video supports YUV 4:4:4/4:2:2/4:2:0/4:1:1 video formats with 8, 10, and 16-bit precision, as well as 4 and 8-bit palettized formats.[32]

WDDM 1.2 supports display-only and render-only WDDM drivers. Also the Microsoft Basic Display Driver[33] and the Microsoft Basic Render Driver are WARP-based, which replaced kernel-mode VGA driver.

WDDM 1.2 supports Direct3D 11 Video Acceleration (D3D11VA), which both DXVA2 decoder and EVR renderer are based on Direct3D 11.[34] Before WDDM 1.2, both the DXVA2 decoder and the EVR renderer are based on Direct3D 9.

In Windows 8, the DWM can using Direct2D 11 and Direct3D 11 with WDDM 1.2 driver.

WDDM 1.0/1.1 only allows rudimentary task scheduling using "batch queue" granularity; improvements to multitasking, as well as fast context switching and support for virtual memory, were initially expected in versions tentatively named WDDM 2.0 and WDDM 2.1, which were announced at WinHEC 2006.[35][36][37]

WDDM 1.3

[edit]

Windows 8.1 includes WDDM 1.3[38] and DXGI 1.3.[39] New additions include the ability to trim DXGI adapter memory usage, multi-plane overlays, overlapping swap chains and swap chain scaling, select backbuffer subregion for swap chain and lower-latency swap chain presentation. Driver feature additions include wireless displays (Miracast), YUV format ranges, cross-adapter resources and GPU engine enumeration capabilities. Graphics kernel performance improvements.[1]

WDDM 2.0

[edit]

Windows 10 includes WDDM 2.0, which is designed to dramatically reduce workload on the kernel-mode driver for GPUs that support virtual memory addressing,[40] to allow multithreading parallelism in the user-mode driver and result in lower CPU utilization.[41][42][43][44] Windows 10 also includes DXGI 1.4.[45]

Direct3D 12 API, announced at Build 2014, requires WDDM 2.0. The new API will do away with automatic resource-management and pipeline-management tasks and allow developers to take full low-level control of adapter memory and rendering states.

The display driver model from Windows 8.1 and Windows Phone have converged into a unified model for Windows 10.[46]

A new memory model is implemented that gives each GPU a per-process virtual address space, this enabled GPU virtual memory and GPU memory paging in WDDM 2.0.[47] Direct addressing of video memory is still supported by WDDMv2 for graphics hardware that requires it, but that is considered a legacy case. IHVs are expected to develop new hardware that supports virtual addressing. Significant changes have been made to the DDI to enable this new memory model.

WDDM 2.1

[edit]

Windows 10 Anniversary Update (version 1607) includes WDDM 2.1, which supports Shader Model 6.0 (mandatory for feature levels 12_0 and 12_1),[48] and DXGI 1.5 which supports HDR10 - a 10-bit high dynamic range, wide gamut format[49] defined by ITU-T Rec. 2100/Rec.2020, and basic variable refresh rates support.[50]

WDDM 2.2

[edit]

Windows 10 Creators Update (version 1703) includes WDDM 2.2, which is tailored for virtual, augmented and mixed reality with stereoscopic rendering for the Windows Mixed Reality platform, and DXGI 1.6.[51]

WDDM 2.3

[edit]

Windows 10 Fall Creators Update (version 1709) includes WDDM 2.3. The following is a list of new features for Windows Display driver development in Windows 10, version 1709:[52]

  • Shader Model 6.1, adding support view instancing and barycentric semantics.[53]
  • Display ColorSpace Transform DDIs provide additional control over color space transforms applied in the post-composition display pipeline.
  • The D3D12 Copy Queue Timestamp Queries feature will allow applications to issue timestamp queries on COPY command lists/queues. These timestamps are specified to function identically to timestamps on other engines.
  • Enhanced Video integration into Direct3D12 Runtime through: hardware accelerated video decoding, content protection and video processing

WDDM 2.4

[edit]

Windows 10 April 2018 Update (version 1803) includes WDDM 2.4. Updates to display driver development in Windows 10 version 1803 include the following features[54].:

  • Shader Model 6.2, adding support for 16-bit scalars and the ability to select the behaviours with denormal values.[55]
  • Indirect Display UMDF class extension, the driver can pass the SRM to the rendering GPU and have a mechanism to query the SRM version being used.
  • IOMMU hardware-based GPU isolation support, increasing security by restricting GPU access to system memory.
  • GPU paravirtualization support, enabling display drivers to provide rendering capabilities to Hyper-V virtualized environments.
  • Brightness, a new interface to support multiple displays that can be set to calibrated nit-based brightness levels.
  • D3D11 bitstream encryption, exposing CENC, CENS, CBC1, and CBCS with 8 or 16 byte initialization vectors.
  • D3D11 and D3D12 video decode histogram, allowing to leverage fixed function hardware for histogram to improve tone mapping quality for HDR/EDR scenarios.
  • D3D12 video decode now supports Decode Tier II, enabling applications to amortize allocation cost and reduce peak memory usage during resolution change.
  • Tiled resource tier and LDA atomics, a new cross node sharing tier to add support for atomic shader instructions working across linked adapter (LDA) nodes, allowing to implement multiple GPU rendering techniques like split frame rendering (SFR).
  • GPU dithering support, allowing the operating system to explicitly request dithering in scenarios where a higher effective bit depth is needed than is physically available on the monitor link, for example for HDR10 over HDMI 2.0.
  • Post-processing color enhancement override, allowing the operating system to request that the driver temporarily disable any post-processing that enhances or alters display colors, for specific application scenarios to enforce colorimetrically accurate color behavior on the display, and safely coexist with OEM or IHV-proprietary display color enhancements.
  • Direct3D12 and Video, new API and DDI to provide access to hardware accelerated video decoding, content protection and video processing.
  • DisplayID, a new DDI, designed to allow the VESA's DisplayID descriptor to be queried from a display controlled by a graphics adapter.
  • GPU performance data, an extension to expose information about the GPU hardware such as temperature, fan speed, clock speeds for engines and memory, memory bandwidth, power draw, and voltages.
  • SupportContextlessPresent, a driver cap to help IHVs onboard new driver.
  • Improvements to External/Removable GPU support in the OS, providing better support to detachable GPUs.
  • Display Diagnostics, with Kernel mode device driver interface changes to allow the driver for a display controller to report diagnostic events to the operating system.
  • Shared graphics power components, allowing non-graphics drivers to participate in the power management of a graphics device.
  • Shared texture improvements, increasing the types of textures that can be shared across processes and Direct3D devices, adding support to monochrome with minimal memory copying.

WDDM 2.5

[edit]

Windows 10 October 2018 Update (Version 1809) Includes WDDM 2.5.[56] Updates to Display driver development in Windows 10, version 1809 include the following features:[57]

  • Shader Model 6.3, adding support for DirectX12 Raytracing (DXR).[58]
  • Raytracing, in order to support hardware-accelerated raytracing in Direct3D 12.
  • Universal Driver Requirements, drivers will need to ensure their DirectX 11 and DirectX12 user-mode drivers and kernel mode drivers, as well other DLL loaded by these components, adhere to the Universal API.
  • SRV-Only Tiled Resource Tier 3, a new capability bit for tiled resources, exposing sparse volume textures without requiring unordered-access and render-target operations support.
  • Render Pass, introducing render pass concept in Direct3D 12, adding new APIs to be run on existing drivers and allow user mode drivers to choose optimal rendering path without heavy CPU penalty.
  • Meta-commands, adding preview support for DirectML, a high-performance, hardware-accelerated DirectX 12 library for machine learning. With Windows 10 version 1903 and newer meta-commands and DirectML are a stable part of Windows.[59]
  • HDR Brightness Compensation, a new SDR brightness boost, raising the reference white of SDR content to the user-desired value, allowing SDR content to be reproduced to a typical 200-240 nits. It also allows reporting if the hardware/driver supports HDR output through FP16 pixel format or only ARGB10 pixel format.
  • SDR White Level, to let the graphics drivers know the SDR white level value that is being applied by the OS compositor for all the SDR content, for a display which is running in HDR mode.
  • Display Synchronization, allowing the operating system to check for display synchronization capabilities if the display is exposed by the driver and prior to enabling the display.
  • Tracked Workloads was also added as an experimental feature to better control the trade-off between quicker processor execution and lower power consumption, but was removed from Windows 10 version 2004 and deprecated from earlier OS versions as part of a security fix.

WDDM 2.6

[edit]

Windows 10 May 2019 Update (Version 1903) includes WDDM 2.6. Updates to display driver development in Windows 10 version 1903 include the following features:[60]

  • Shader Model 6.4, adding support low-precision packed dot product intrinsics and for library sub-objects to simplify ray-tracing.[61]
  • Super Wet Ink, allowing the creation of textures in formats and modes the IHVs doesn't natively support, resolving them as a resource projection to a format the hardware/drivers natively support, allowing internal drivers optimizations.
  • Variable Rate Shading, also known as coarse pixel shading, a mechanism to enable allocation of rendering performance/power at varying rates across rendered images. It comes with two tiers (tier 1 and tier 2).
  • Collect Diagnostic Info, allowing the operating system to collect a private data from drivers for both rendering and display functions. This new feature is a requirement in WDDM 2.6.
  • Background Processing, allowing user mode drivers to express desired threading behavior, and the runtime to control/monitor it. APIs allow apps to adjust what amount of background processing is appropriate for their workloads and when to perform that work.
  • Driver Hot Update, reducing server downtime and allowing driver security hot patch to the kernel mode driver.
  • Microsoft Compute Driver Model (MCDM), for AI processors such as NPU.

WDDM 2.7

[edit]

Windows 10 May 2020 Update[62] (Version 2004) includes WDDM 2.7. Updates to display driver development in Windows 10 version 2004 include the following features:[63]

  • Shader Model 6.5, adding support to the new pipeline capabilities as well additional Wave intrinsics.[64]
  • Hardware-accelerated GPU scheduing: masked as an additional option in the system settings, when enabled offloads high-frequency tasks to a dedicated GPU-based scheduling processor, reducing CPU scheduling overhead. Requires ad-hoc hardware and driver support.[65]
  • Sampler Feedback, allowing a finer tune of the resources usage in a scene.[66] It comes with two tiers (tier 0.9 and tier 1.0).[67]
  • DirectX Raytracing (DXR) Tier 1.1, introducing inline ray-tracing, indirect rays dispatching, increasing the state object without the need to create a new one, and additional vertex formats for acceleration structures.[68]
  • Mesh and Amplification Shaders Stages, a new optional geometry pipeline replacing the traditional pipeline (Input Assembler-Vertex-Hull-Tesselator-Domain-Geometry and Stream Output stages).[69]
  • Improved memory allocation control, with better residency control and the possibility to not explicitly zeroing newly created heaps.[70]
  • Direct3D 9 resource interop, allowing projecting a Direct3D 9 resource on a Direct3D 12 application.[71]
  • Direct3D 12 Video Protected Resource support, allowing play protected content in a Direct3D 12 application.[72]

WDDM 2.8

[edit]

Windows 10 Insider Preview Manganese included WDDM 2.8, but no driver was ever publicly demonstrated to support it and it has been skipped for "Iron" and "Cobalt" development releases.

WDDM 2.9

[edit]

WDDM 2.9 in Windows 10 Insider Preview "Iron" will bring support for GPU hardware acceleration to the Windows Subsystem for Linux 2 (WSL 2)[73] and support for feature level 12_2[74] and HLSL Shader Model 6.6.[75]

WDDM 3.0

[edit]

Windows 11 RTM Final Retail release includes WDDM 3.0,[76][77] which improves graphics architecture in Windows Subsystem for Linux[78] and in Windows DWM adding:[79]

  • User mode driver compiled for Linux in the WSL package.
  • Host driver mounted in Linux
  • Variable refresh rate (supports HDMI Forum VRR and VESA Adaptive Sync)[80]
  • HDMI Auto Low Latency Mode
  • Auto color management[81]
  • Auto HDR
  • Direct3D 12 video encoding[82]
  • Hardware flip queue[83]
  • Allow passthrough of CTA blocks and DisplayID blocks of EDID[84]

WDDM 3.1

[edit]

Windows 11 2022 Update (version 22H2) includes WDDM 3.1.[85][86]

  • Shader Model 6.7[87]
  • IOMMU DMA remapping[88]
  • Sharing the backing store with KMD[89]

WDDM 3.2

[edit]

Windows 11 2024 Update (version 24H2) includes WDDM 3.2.[90]

  • Shader Model 6.8[91]
  • Dirty bit tracking
  • Live migration on GPU-P devices
  • Native GPU fence objects
  • User-mode work submission
  • D3D12 AV1 video encoding
  • Work graphs[92]


References

[edit]
  1. ^ "Windows Display Driver Model (WDDM) Design Guide". MSDN. Microsoft. Retrieved 19 February 2015.
  2. ^ a b c d e "Windows Vista Display Driver Model". MSDN. Microsoft. July 2006. Archived from the original on 2010-05-06. Retrieved 9 December 2013.
  3. ^ "XPDM vs. WDDM". MSDN. Microsoft. 16 November 2013. Retrieved 16 December 2013.
  4. ^ "Windows 2000 Display Driver Model (XDDM) Design Guide". Windows Dev Center - Hardware. Microsoft. 16 November 2013. Retrieved 9 December 2013.
  5. ^ "Roadmap for Developing Drivers for the Windows 2000 Display Driver Model (XDDM)". Windows Dev Center - Hardware. Microsoft. 16 November 2013. Retrieved 16 December 2013. XDDM and VGA drivers will not compile on Windows 8 and later versions
  6. ^ "Graphics Memory Reporting through WDDM". MSDN. Microsoft. 9 January 2007. Retrieved 9 December 2013.
  7. ^ Schechter, Greg (2 April 2006). "The role of the Windows Display Driver Model in the DWM". Greg Schechter's Blog. Microsoft. Archived from the original on 20 April 2010. Retrieved 9 December 2013.
  8. ^ "Cross Process Resource Sharing". MSDN. Microsoft. 10 December 2009. Retrieved 9 December 2013.
  9. ^ "Timeout Detection and Recovery of GPUs through WDDM". Timeout Detection and Recovery: Microsoft. Archived from the original on 6 September 2011. Retrieved 4 September 2011.
  10. ^ a b c d "Graphics Guide for Windows 7". Microsoft. 12 June 2009.
  11. ^ Intel excuse for no GMA900 WDDM driver: no "HW Scheduler" no driver, Beyond3D, October 26, 2006.
  12. ^ a b "MultiMonitor Support and Windows Vista". Retrieved 20 October 2007.
  13. ^ Pournelle, Jerry (2004). "WinHEC: The Future of Windows". BYTE. UBM Technology Group. Archived from the original on October 15, 2024. Retrieved December 31, 2025. Another big change: LDDM will only allow a single display driver at a time. You can still have multiple display adapters, but they'll have to share a single driver—effectively meaning they'll have to be from the same manufacturer. That seems a reasonable restriction.
  14. ^ Blythe, David. "Working With the Windows 7 Graphics Architecture". WinHEC 2008. Microsoft. Archived from the original on October 20, 2013. Retrieved 9 December 2013.
  15. ^ Are there Control Panel features that were available under Windows XP that are no longer available on Windows Vista?[link removed]
  16. ^ Stretched Desktop or Spanning Mode Not Available in Catalyst Control Center Under Windows Vista Archived November 17, 2009, at the Wayback Machine
  17. ^ "Description of DualView in Windows XP (Revision 1.5)". Support. Microsoft. 15 January 2006. Retrieved 9 December 2013.
  18. ^ "GDI Hardware Acceleration". MSDN. Microsoft. Retrieved 14 June 2009.
  19. ^ "DXVA-HD DDI". MSDN. Microsoft. Retrieved 13 June 2009.
  20. ^ "Overlay DDI". MSDN. Microsoft. Retrieved 13 June 2009.
  21. ^ "Multiple Monitors and Video Present Networks". MSDN. Microsoft. Retrieved 14 July 2010.
  22. ^ Zheng, Long (2008-10-29). "Windows 7 DWM cuts memory consumption by 50%". istartedsomething. Retrieved 2026-06-13.
  23. ^ Schechter, Greg (3 May 2006). "Redirecting GDI, DirectX, and WPF applications". Greg Schechter's Blog. Microsoft. Archived from the original on 5 March 2010. Retrieved 9 December 2013.
  24. ^ Chitre, Ameet (25 August 2009). Sinofsky, Steven (ed.). "Engineering Windows 7 Graphics Performance". Engineering Windows 7. Microsoft. Retrieved 9 December 2013.
  25. ^ Mulcahy, Tom (11 February 2009). "Windows And Video Memory". Zemblanity. Microsoft. Retrieved 9 December 2013.
  26. ^ Olsen, Thomas (29 October 2008). "Introducing the Microsoft Direct2D API". Tom's Blog. Microsoft. Retrieved 9 December 2013.
  27. ^ Mark Lawrence (25 November 2009). "Internet Explorer announces to use DirectWrite & Direct2D (comment from Microsoft official)". Archived from the original on 2014-04-08.
  28. ^ "Windows Developer Preview - New for Display devices". MSDN. Microsoft. 16 November 2013. Retrieved 9 December 2013.
  29. ^ a b "Windows Display Driver Model Enhancements in Windows Developer Preview". MSDN. Microsoft. 28 September 2012. Retrieved 9 December 2013.
  30. ^ "DXGI 1.2 Improvements". MSDN. Microsoft. 16 November 2013. Retrieved 9 December 2013.
  31. ^ "DXGI_Graphics_Preemption_Granularity Enumeration". MSDN. Microsoft. 16 November 2013. Retrieved 9 December 2013.
  32. ^ "DXGI_FORMAT enumeration". MSDN. Microsoft. 16 November 2013. Retrieved 9 December 2013.
  33. ^ "Microsoft Basic Display Driver - Windows drivers". 27 June 2024.
  34. ^ EliotSeattle. "Direct3D 11 Video Playback Improvements - Windows drivers". learn.microsoft.com. Retrieved 2026-05-30.
  35. ^ Al-Kady, Nabeel. "Display Driver Logistics And Testing". WinHEC 2006. Microsoft. Retrieved 9 December 2013.
  36. ^ Pronovost, Steve. "Windows Display Driver Model (WDDM) v2 And Beyond". WinHEC 2006. Microsoft. Retrieved 9 December 2013.
  37. ^ Dan Warne (June 1, 2006). "Windows graphics system to be overhauled". APC Magazine. Retrieved 20 February 2015.
  38. ^ "What's new for Windows 8.1 Preview display drivers (WDDM 1.3)". MSDN. Microsoft. 16 November 2013. Retrieved 9 December 2013.
  39. ^ "DXGI 1.3 Improvements". MSDN. Microsoft. 16 November 2013. Retrieved 9 December 2013.
  40. ^ "What's new for Windows 10 Insider Preview display drivers (WDDM 2.0)". Microsoft. Retrieved 3 June 2015.
  41. ^ McMullen, Max (2 April 2014). Direct3D 12 API Preview. MSDN. Retrieved 3 June 2015.
  42. ^ Moreton, Henry (2014-03-20). "DirectX 12: A Major Stride for Gaming | NVIDIA Blog". Blogs.nvidia.com. Retrieved 2014-03-26.
  43. ^ "DirectX 12 - DirectX Developer Blog - Site Home - MSDN Blogs". Blogs.msdn.com. 2014-03-20. Retrieved 2014-03-26.
  44. ^ Smith, Ryan (6 February 2015). "The DirectX 12 Performance Preview: AMD, NVIDIA, & Star Swarm". AnandTech. Purch.{{cite web}}: CS1 maint: deprecated archival service (link)
  45. ^ MSDN - DXGI 1.4 Improvements
  46. ^ tedhudek. "What's new in driver development". docs.microsoft.com. Retrieved 2018-10-08.
  47. ^ lorihollasch. "GPU Virtual Memory in WDDM 2.0 - Windows drivers". learn.microsoft.com. Retrieved 2025-06-15.
  48. ^ "HLSL Shader Model 6.0 - Win32 apps". 25 August 2021.
  49. ^ "High Dynamic Range and Wide Color Gamut (Windows)". msdn.microsoft.com. Archived from the original on 2016-09-13.
  50. ^ "Variable refresh rate displays - Win32 apps". 6 January 2021.
  51. ^ "Channel9 has joined Microsoft Learn".
  52. ^ "Driver development additions for Windows 10, version 1709 - Display". docs.microsoft.com. Retrieved 2020-04-14.
  53. ^ "Shader Model 6.1". github.com/microsoft/DirectXShaderCompiler. Retrieved 2017-12-01.
  54. ^ "What's new in Windows 10, version 1803 - Display". docs.microsoft.com. Archived from the original on 2020-07-20. Retrieved 2020-04-28.
  55. ^ "Shader Model 6.2". github.com/microsoft/DirectXShaderCompiler. Retrieved 2017-12-01.
  56. ^ "Features added in prior WDDM 2.X versions - WDDM 2.5". Microsoft Docs. Retrieved 2020-03-28.
  57. ^ "Windows Drivers - What's new in Windows 10, version 1809 - Display". Microsoft Docs. Archived from the original on 2020-07-20. Retrieved 2020-04-28.
  58. ^ "Shader Model 6.3". github.com/microsoft/DirectXShaderCompiler. Retrieved 2019-03-11.
  59. ^ "Getting Started with DirectML". github.com/microsoft/DirectML. 26 November 2021.
  60. ^ "Features added in prior WDDM 2.X versions - WDDM 2.6". docs.microsoft.com. Retrieved 2020-03-24.
  61. ^ "Shader Model 6.4". github.com/microsoft/DirectXShaderCompiler. Retrieved 2019-04-11.
  62. ^ "Dev Preview of New DirectX 12 Features". devblogs.microsoft.com. 28 October 2019. Retrieved 2019-10-28.
  63. ^ "What's new for Windows 10 display and graphics drivers". docs.microsoft.com. Retrieved 2020-05-12.
  64. ^ "HLSL Shader Model 6.5". microsoft.github.io. Retrieved 2019-10-15.
  65. ^ "Hardware Accelerated GPU Scheduling". devblogs.microsoft.com. 30 June 2020. Retrieved 2020-06-30.
  66. ^ "Coming to DirectX 12— Sampler Feedback: some useful once-hidden data, unlocked". devblogs.microsoft.com. 4 November 2019. Retrieved 2019-11-04.
  67. ^ "DirectX-Specs - Sampler Feedback - Feature Support". microsoft.github.io. Retrieved 2019-11-04.
  68. ^ "DirectX Raytracing (DXR) Tier 1.1". devblogs.microsoft.com. 6 November 2019. Retrieved 2019-11-06.
  69. ^ "Coming to DirectX 12— Mesh Shaders and Amplification Shaders: Reinventing the Geometry Pipeline". devblogs.microsoft.com. 8 November 2019. Retrieved 2019-11-08.
  70. ^ "Coming to DirectX 12: More control over memory allocation". devblogs.microsoft.com. 11 November 2019. Retrieved 2019-11-11.
  71. ^ "Coming to DirectX 12: D3D9On12 and D3D11On12 Resource Interop APIs". devblogs.microsoft.com. 13 November 2019. Retrieved 2019-11-13.
  72. ^ "D3D12 Video Protected Resource Support". microsoft.github.io. Retrieved 2019-05-29.
  73. ^ "DirectX ❤ Linux". devblogs.microsoft.com. 19 May 2020. Retrieved 2020-05-19.
  74. ^ "New in DirectX— Feature Level 12_2". 27 August 2020.
  75. ^ "Announcing HLSL Shader Model 6.6". 20 April 2021.
  76. ^ "How to get Windows 11". 4 October 2021.
  77. ^ "Download Windows 11". Microsoft.
  78. ^ "WSL Graphics Architecture". xdc2020.x.org. Archived from the original on 2021-10-08. Retrieved 2020-09-16.
  79. ^ "What's new for Windows 11 display and graphics drivers - Windows drivers". 22 August 2024.
  80. ^ "Dynamic refresh rate – Get the best of both worlds". 28 June 2021.
  81. ^ Carvalho, Ana Marta (2022-10-12). "Advancing the State of Color Management in Windows". DirectX Developer Blog. Retrieved 2026-06-02.
  82. ^ "D3D12 video encoding - Windows drivers". 5 March 2022.
  83. ^ "Hardware flip queue - Windows drivers". 26 June 2024.
  84. ^ GrantMeStrength. "Windows hardware display color calibration pipeline - Win32 apps". learn.microsoft.com. Retrieved 2026-07-05.
  85. ^ "Available today: The Windows 11 2022 Update". 20 September 2022.
  86. ^ "Download Windows 11". Microsoft.
  87. ^ "HLSL Shader Model 6.7".
  88. ^ lorihollasch. "IOMMU DMA remapping - Windows drivers". docs.microsoft.com. Retrieved 2022-07-24.
  89. ^ "Sharing the backing store with KMD - Windows drivers". 22 August 2024.
  90. ^ "What's New in Driver Development for Windows 11, Version 24H2 - Windows drivers". 18 September 2024.
  91. ^ "DirectX-Specs".
  92. ^ "Work Graphs - Windows drivers". 22 May 2024.

Source: Wikipedia. Article content is retrieved live through the MediaWiki API.

No preview image
Wikipedia

Windows Display Driver Model

Windows Display Driver Model (WDDM, initially LDDM as Longhorn Display Driver Model and then WVDDM in times of Windows Vista) is the graphic driver architecture for video card drivers running Microsoft Windows versions beginning with Windows Vista. It is a replacement for the previous display driver model of Windows 2000 (called XDDM) and Windows XP (called XPDM) and is aimed at enabling better performance graphics and new graphics functionality and stability. Display drivers in Windows Vista and Windows 7 can choose to either adhere to WDDM or to XDDM. With the removal of XDDM from Windows 8, however, WDDM became the unified option. In Windows 2000 and Windows XP, the XDDM/XPDM is based on WDM. WDDM provides the functionality required to render the desktop and applications using Desktop Window Manager, a compositing window manager running on top of Direct3D. It also supports new DXGI interfaces required for basic device management and creation. The WDDM specification requires at least Direct3D 9-capable video card and the display driver must implement the device driver interfaces for the Direct3D 9Ex runtime in order to run legacy Direct3D applications; it may optionally implement runtime interfaces for Direct3D 10 and higher.

MORE →
No preview image
Wikipedia

DirectX Graphics Infrastructure

DirectX Graphics Infrastructure (DXGI) is a user-mode component of Microsoft Windows (for Windows Vista and above) which provides a mapping between particular graphics APIs such as Direct3D 10.0 and above (known in DXGI parlance as producers) and the graphics kernel, which in turn interfaces with the user-mode Windows Display Driver Model driver. DXGI provides objects for tasks such as enumerating graphics adapters and monitors, enumerating display modes, choosing buffer formats, sharing resources between processes (such as between applications and the Desktop Window Manager), and presenting rendered frames to a window or monitor for display. Both Direct3D 10 and OpenGL applications in Windows Vista work through DXGI. Windows 8 introduced a notably useful DXGI-based API called Desktop Duplication API for hardware accelerated video capture using DirectX. Using it with a hardware video encoder provides a low-latency, high-performance solution for screen capturing and encoding, freeing up the CPU for gaming or other tasks such as Miracast screencasting, streaming, remote desktop scenarios. DXGI 1.1 added surface sharing between the various Windows graphics API. The newest version is DXGI 1.6, introduced with Windows 10 Creators Update and updated with Windows 10 Fall Creators Update. DXGI 2 preview was released alongside the Oculus Rift SDK, containing improvements for stereoscopic rendering. DirectX Graphics Infrastructure(''DXGI") is a Microsoft Windows graphics infrastructure that provides support for low level graphics API shared operations. It offers the ability to enumerate graphics adapters and the supported display modes, select buffer formats, share graphics resources between processes, and present the frames rendered to the displays.The Direct3D 10 graphics architecture is the introduction of DXGI, which takes care of these low-level tasks, and it is a separation from the Direct3D runtime.

MORE →
Wikipedia

ScRGB

scRGB is a wide color gamut RGB color space created by Microsoft and HP that uses the same color primaries and white/black points as the sRGB color space but allows coordinates below zero and greater than one. The full range is −0.5 through just less than +7.5. Negative numbers enables scRGB to encompass most of the CIE 1931 color space while maintaining simplicity and backward compatibility with sRGB by not changing the primary colors. However this means approximately 80% of the scRGB color space consists of imaginary colors. Numbers greater than 1.0 allow high dynamic range images to be represented, though the dynamic range is less than other formats.

MORE →
No preview image
Wikipedia

Windows Vista

Windows Vista is a major release of the Windows NT operating system developed by Microsoft. It was the direct successor to Windows XP, released five years earlier, which was then the longest time span between successive releases of Microsoft Windows. It was released to manufacturing on November 8, 2006, and over the following two months, it was released in stages to business customers, original equipment manufacturers (OEMs), and retail channels. On January 30, 2007, it was released internationally and was made available for purchase and download from the Windows Marketplace; it is the first release of Windows to be made available through a digital distribution platform. Development of Windows Vista began in 2001 under the codename "Longhorn"; originally envisioned as a minor successor to Windows XP, it gradually included numerous new features from the then-next major release of Windows codenamed "Blackcomb", after which it was repositioned as a major release of Windows, and it subsequently underwent a period of protracted development that was unprecedented for Microsoft. Most new features were prominently based on a new presentation layer codenamed Avalon, a new communications architecture codenamed Indigo, and a relational storage platform codenamed WinFS — all built on the .NET Framework; however, this proved to be untenable due to incompleteness of technologies and ways in which new features were added, and Microsoft reset the project in 2004. Many features were eventually reimplemented after the reset, but Microsoft ceased using managed code to develop the operating system. New features of Windows Vista include a graphical user interface and visual style referred to as Windows Aero; a content index and desktop search platform called Windows Search; new peer-to-peer technologies to simplify sharing files and media between computers and devices on a home network; and new multimedia tools such as Windows DVD Maker. Windows Vista included version 3.0 of the .NET Framework, allowing software developers to write applications without traditional Windows APIs. There are major architectural overhauls to audio, display, network, and print sub-systems; deployment, installation, servicing, and startup procedures are also revised. It is the first release of Windows built on Microsoft's Trustworthy Computing initiative and emphasized security with the introduction of many new security and safety features such as BitLocker and User Account Control. General reception to Windows Vista was mixed; while the design quality and addition of new features earned positive reception, Windows Vista was the subject of frequent criticism and negative press review. Criticism of Windows Vista focused on driver, peripheral, and program incompatibility; digital rights management; excessive authorization from the new User Account Control; inordinately high system requirements when contrasted with Windows XP; its protracted development; longer boot time; and more restrictive product licensing. Windows Vista deployment and satisfaction rates were consequently lower than those of Windows XP, and it is considered a market failure; however, its use surpassed Microsoft's pre-launch two-year-out expectations of achieving 200 million users (with an estimated 330 million users by 2009). Two service packs were released, in 2008 and 2009 respectively. Windows Vista was succeeded by Windows 7 in 2009, and on October 22, 2010, Microsoft ceased retail distribution of Windows Vista; OEM supply ceased a year later. Mainstream support for Windows Vista ended on April 10, 2012, and extended support ended on April 11, 2017.

MORE →
TOPIC OF THE DAY

Greenwood / Black Wall Street

Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.

MORE →
TRIVIA QUESTION OF THE DAY

What prosperous Tulsa district became widely known as “Black Wall Street”?

The Greenwood District.