Lines Matching full:drivers
19 * A graphics device might be supported by different drivers, but only one
21 * graphics drivers, such as EFI-GOP or VESA, early during the boot process.
25 * ownership of framebuffer memory and hand-over between drivers.
27 * Graphics drivers should call aperture_remove_conflicting_devices()
63 * The call to aperture_remove_conflicting_devices() releases drivers that
70 * device drivers can also call aperture_remove_conflicting_pci_devices() and
71 * let the function detect the apertures automatically. Device drivers without
75 * Drivers that are susceptible to being removed by other drivers, such as
76 * generic EFI or VESA drivers, have to register themselves as owners of their
124 * another driver. This only works for platform drivers that support hot
206 * to do for firmware-based fb drivers, such as EFI, VESA or VGA. After in aperture_detach_platform_device()
212 * If the aperture helpers ever need to handle native drivers, this call in aperture_detach_platform_device()
292 * Drivers for devices that don't have a generic driver will never in aperture_remove_conflicting_devices()
312 * PCI graphics device with framebuffers in non-BAR locations. Drivers
320 * WARNING: Apparently we must remove graphics drivers before calling