xorg doesn't try to autoload the omap xorg driver at omapdrm enabled devices
Bug #1040405 reported by
Ricardo Salveti
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Fix Released
|
High
|
Ricardo Salveti |
Bug Description
There's currently the support for the xf86-video-omap driver, which enable additional features for omapdrm compatible devices, but it's not yet loaded automatically by the xserver.
The main reason is that the omapdrm device is a real platform device, without any specific busID to be used by the server. As current Xorg either tries to identify by using a bus like PCI, or by investigating the driver's ID, there's no easy way to make it also load drivers for platform devices (the device id is specific to platforms).
Related branches
Changed in xorg-server (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Ricardo Salveti (rsalveti) |
To post a comment you must log in.
This patch adds the support for the omap X11 driver autoload following the same solution we have for other a ARM boards (which we also used for our previous cycle).
At the end there's a small change as well to make xorg to use the recently added platform probe functions, by trying to probe the driver in case there's only one platform device available and without a valid busID (case of Omap3 and Omap4 based devices). This will allow the platformProbe to be used by the omap X11 driver, fixing the behavior of loading more than one screen by default (one for omap and another for fbdev).
To make the upstream code to work with the platform bus support by default, we'd still need some other changes to land, and a solution which we could find one single ID that could be used by all platform devices, so this workaround should be enough at least for Quantal.