Driver Atlas

Graphics driver compatibility reference

How adapter identity, hardware architecture, display interfaces, package declarations, and monitor capabilities meet.

Graphics driver compatibility reference

Compatibility is not a family label

A graphics package is compatible within a declared relationship among an adapter, hardware architecture, component model, and display interfaces. A product family can span revisions or variants, so its name is not a substitute for package matching records and component contracts.

Different layers expose different capabilities

A GPU can expose graphics API features, memory behavior, display engines, and connector interfaces. A monitor exposes timing and pixel capabilities. The graphics driver connects those records but does not erase the distinction between adapter and sink.

Package declarations establish scope

Information files, catalogs, supported identifiers, architecture fields, and release notes describe where a package belongs. A package can support a broad class while optional features, modes, or companion components vary across configurations.

Runtime compatibility has another boundary

Matching and installation establish a relationship; runtime interfaces then expose commands, memory, modes, and presentation. A compatibility statement is strongest when it says whether it refers to package matching, API exposure, display modes, or a specific component contract.

Reference facts

Compatibility inputs
Adapter, architecture, component model, and display path
Sink boundary
Monitor timing and pixel capabilities are separate from GPU records
Runtime boundary
Package match, API, mode, and presentation contracts differ

Questions and answers

Does a package that matches the GPU support every monitor?

No. Monitor capabilities, connector paths, timing, and display contracts are additional relationships.

Is API compatibility the same as package compatibility?

No. Package matching and runtime API exposure are related but distinct boundaries.

Can a broad graphics package support optional features differently?

Yes. Optional hardware and companion components can change the features exposed in a particular configuration.

Further reading