I'm looking for the mechanism in the kernel that makes the decision to load the efifb driver over a dri one. Any tips? I've got a machine here that loads efifb and prevents dri drivers from loading.
thanks, Chris
On Mon, May 27, 2013 at 5:42 PM, Christopher Harvey charvey@matrox.com wrote:
I'm looking for the mechanism in the kernel that makes the decision to load the efifb driver over a dri one. Any tips? I've got a machine here that loads efifb and prevents dri drivers from loading.
Once the drm driver loads it should kick out any firmware framebuffer driver (like the efifb). See e.g. i915_kick_out_firmware_fb in drm/i915_dma.c Ignoring the occasional deadlock in the fbcon layer, this works.
Cheers, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch
Hi
On Mon, May 27, 2013 at 5:42 PM, Christopher Harvey charvey@matrox.com wrote:
I'm looking for the mechanism in the kernel that makes the decision to load the efifb driver over a dri one. Any tips? I've got a machine here that loads efifb and prevents dri drivers from loading.
If you want to use efifb over DRM drivers, you must unload the DRM drivers or blacklist them. The kernel is designed to prefer real hardware drivers over generic fallbacks (like efifb, vesafb, ...).
See ./drivers/video/fbmem.c remove_conflicting_framebuffers(). This is called by DRM drivers to kick out any conflicting fbdev drivers.
Cheers David
dri-devel@lists.freedesktop.org
-
Christopher Harvey -
Daniel Vetter -
David Herrmann