Bug 42848 - The poulsbo driver conflicts with the psb_gfx driver
Summary: The poulsbo driver conflicts with the psb_gfx driver
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri-intel@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-02 20:03 UTC by bodhi.zazen
Modified: 2012-03-24 23:25 UTC (History)
2 users (show)

See Also:
Kernel Version:
Tree: Mainline
Regression: No


Attachments

Description bodhi.zazen 2012-03-02 20:03:21 UTC
This is a bug report on the intel gma500

There is a staging driver, psb_gfx and it conflicts with the poulsbo driver.

CONFIG_STUB_POULSBO=m

Conflicts with the (staging) psb_gfx

CONFIG_DRM_GMA500=y

If you build both drivers, either as modules or built in, as is default with most major distros, the graphics (psb_gfx) fails. You then have to manually remove the poulsbo driver and load the psb_gfx

rmmod poulsbo
modprobe psb_gfx

And the psb_gfx module loads.

What information can be provided to resolve this conflict ?

Related bug reports

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244

https://bugzilla.redhat.com/show_bug.cgi?id=785053
Comment 1 bodhi.zazen 2012-03-02 22:57:12 UTC
Please see this comment

"The poulsbo driver is just a stub module that enables the acpi video support for the panel brightness.
This feature is already present inside the psb_gfx driver.

The poulsbo module is loaded before the psb_gfx 'stealing' the pciid and not allowing the psb_gfx module
to start up and open the framebuffer.  that's why there is a conflict.

I don't see any reason to preserve the stub poulsbo, psb_gfx already provides brightness support for every
gma500/600 device. Is not useful also for the EMGD binary drivers provided by Intel."

From https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244
Comment 2 Daniel Vetter 2012-03-24 23:25:05 UTC
The stub driver is on track to get removed, marking as fixed.

Note You need to log in before you can comment on or make changes to this bug.