drm_module_p...r_if_modeset(9)
π drm_module_pci_driver_if_modeset(9)
okay so bestie, welcome to the Kernel API Manual β¨ this one is section 9, and the function/thing we're talking about is literally named drm_module_pci_driver_if_modeset (the header up top shortens it to drm_module_p...r_if_modeset(9) because apparently even the manpage got tired halfway through typing it π). Let's get into it π«Ά
πΈ NAME πΈ
drm_module_pci_driver_if_modeset β Register a DRM driver for PCI-based devices β¨
π SYNOPSIS π
drm_module_pci_driver_if_modeset (__pci_drv , __modeset );
π¦ ARGUMENTS π¦
__pci_drvβ the PCI driver structure, the main character of this whole situation π__modesetβ an additional parameter that disables the driver, iykyk π
π DESCRIPTION π
π¨ bestie listen β this macro is deprecated and it's only hanging around for existing drivers. It's giving legacy energy fr fr. For new drivers, use drm_module_pci_driver instead, periodt. π
So what does it actually do? It registers a DRM driver for devices on the PCI bus β¨
The helper macro behaves like drm_module_pci_driver with an additional driver-specific flag. And the flag's whole vibe check goes like this:
- If
__modesetis0, the driver has been disabled π - If
__modesetis-1, the driver state depends on the global DRM state π - For all other values, the PCI driver has been enabled π₯
And the default should be -1 β that's the one to go with unless you've got a reason, ngl π«Ά
π SEE ALSO π
- Kernel file
./include/drm/drm_module.hβoverview(9) drm_module_pci_driver(9)drm_module_platform_driver(9)
that's the whole page, no cap π§π it lives under ./include/drm and the manpage date is October 2026, filed under the name drm_module_p...r_if_modeset(9) β go forth and register your PCI drivers responsibly, bestie πππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms