7fca1dd909
Use the regular fbdev helpers for framebuffer I/O instead of DRM's helpers. Gma500 does not use damage handling, so DRM's fbdev helpers are mere wrappers around the fbdev code. By using fbdev helpers directly within each DRM fbdev emulation, we can eventually remove DRM's wrapper functions entirely. v4: * use initializer macros for struct fb_ops v2: * use FB_IO_HELPERS option Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de> Acked-by: Sam Ravnborg <sam@ravnborg.org> Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com> Link: https://patchwork.freedesktop.org/patch/msgid/20230530151228.22979-6-tzimmermann@suse.de
19 lines
644 B
Plaintext
19 lines
644 B
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
config DRM_GMA500
|
|
tristate "Intel GMA500/600/3600/3650 KMS Framebuffer"
|
|
depends on DRM && PCI && X86 && MMU
|
|
select DRM_KMS_HELPER
|
|
select FB_IO_HELPERS if DRM_FBDEV_EMULATION
|
|
select I2C
|
|
select I2C_ALGOBIT
|
|
# GMA500 depends on ACPI_VIDEO when ACPI is enabled, just like i915
|
|
select ACPI_VIDEO if ACPI
|
|
select BACKLIGHT_CLASS_DEVICE if ACPI
|
|
select INPUT if ACPI
|
|
select X86_PLATFORM_DEVICES if ACPI
|
|
select ACPI_WMI if ACPI
|
|
help
|
|
Say yes for an experimental 2D KMS framebuffer driver for the
|
|
Intel GMA500 (Poulsbo), Intel GMA600 (Moorestown/Oak Trail) and
|
|
Intel GMA3600/3650 (Cedar Trail).
|