[Precise][PATCH 0/2] Disable CONFIG_STUB_POULSBO in favor of CONFIG_DRM_PSB

Tim Gardner rtg.canonical at gmail.com
Tue Mar 13 23:05:36 UTC 2012


On 03/13/2012 03:15 PM, leann.ogasawara at canonical.com wrote:
> From: Leann Ogasawara<leann.ogasawara at canonical.com>
>
> BugLink: http://bugs.launchpad.net/bugs/899244
>
> There is a staging driver, psb_gfX (CONFIG_DRM_PSB), which supports
> Intel GMA500 cards.  This driver has moved out of staging as of v3.3.
> We currently have this staging driver enabled.  Unfortunately,
> this driver conflicts with the poulsbo driver (CONFIG_STUB_POULSBO). The
> poulsbo driver supports cards 8086:8108 and 8086:8109 both of which are
> also supported by the psb_gfx driver.  It has been requested we disable
> the poulsbo driver in favor of the psb_gfx driver.  Users owning 8086:8108
> confirm they need to use the psb_gfx driver to have proper graphics
> support.  If they try to use the poulsbo driver, X fails.
>
> I'd committed this change earlier in the cycle but there were concerns
> about completely disabling the pouslbo driver and an alternative
> solution of blacklisting the poulsbo driver in module-init-tools might
> be a better solution.  However, having received confirmation from users
> that their devices are better supported by psb_gfx, it seems best to
> just disable the poulsbo driver rather than blacklist it in
> module-init-tools.
>
> I wanted to circulate this to the list to get feedback before applying.
>
> There is also an upstream bug to track the driver's conflicting:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=42848
>
> Thanks,
> Leann
>
> Leann Ogasawara (2):
>    UBUNTU: [Config] Disable CONFIG_STUB_POULSBO
>    UBUNTU: [Config] Add CONFIG_DRM_PSB check to enforcer
>
>   debian.master/config/config.common.ubuntu |    2 +-
>   debian.master/config/enforce              |    6 ++++++
>   2 files changed, 7 insertions(+), 1 deletions(-)
>

I'm exploring the possibility of backporting the 3.3-rc7 gma500. The OEM 
crew are gonna try the upstream kernel tomorrow (which has a key boot 
time fix). If that works, then it might make sense to pluck the 3.3 
driver plus some DRM support cruft.

rtg
-- 
Tim Gardner tim.gardner at canonical.com




More information about the kernel-team mailing list