drivers/gpu/drm/mgag200/Kconfig

Source file repositories/reference/linux-study-clean/drivers/gpu/drm/mgag200/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/gpu/drm/mgag200/Kconfig
Extension: [no extension]
Size: 886 bytes
Lines: 25
Domain: Driver Families
Bucket: drivers/gpu
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
config DRM_MGAG200
	tristate "Matrox G200"
	depends on DRM && PCI
	select DRM_CLIENT_SELECTION
	select DRM_GEM_SHMEM_HELPER
	select DRM_KMS_HELPER
	select I2C
	select I2C_ALGOBIT
	help
	 This is a KMS driver for Matrox G200 chips. It supports the original
	 MGA G200 desktop chips and the server variants. It requires 0.3.0
	 of the modesetting userspace driver, and a version of mga driver
	 that will fail on KMS enabled devices.

config DRM_MGAG200_DISABLE_WRITECOMBINE
	bool "Disable Write Combine mapping of VRAM"
	depends on DRM_MGAG200 && PREEMPT_RT
	help
	  The VRAM of the G200 is mapped with Write-Combine to improve
	  performances. This can interfere with real-time tasks; even if they
	  are running on other CPU cores than the graphics output.
	  Enable this option only if you run realtime tasks on a server with a
	  Matrox G200.

Annotation

Atlas domain: Driver Families / drivers/gpu.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.