Bug 3208 - Enable GMA500 for -noemgd meta-intel BSPs
Summary: Enable GMA500 for -noemgd meta-intel BSPs
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.4
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.4 M3
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-10-02 19:58 UTC by Darren Hart
Modified: 2013-01-29 06:05 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darren Hart 2012-10-02 19:58:37 UTC 
The VESA fallback used for the meta-intel -noemgd BSPs is dependent on BIOS (doesn't work with EFI) and doesn't take advantage of the recent open source driver alternatives for the hardware. This is a feature request to enable GMA500 as the default for the -noemgd BSPs in meta-intel.
Comment 1 Nitin Kamble 2013-01-17 23:20:19 UTC 
I tried the gma500/gma600 driver for crownbay-noemgd BSP. The driver detects the graphics h/w but it is not able to detect any connected displays. I exchanged few emails with Alan Cox for this, and as per him currently the gma500 driver does not support the tunnel creek based boards. That means the gma500 driver does not work for our crownbay, fri2 & sys940 BSPs.

  I also tried the gma500 driver for the newly created emenlow-noemgd BSP. And it is working as expected. 

  I have sent out a pull request with commits adding gma500 support to v3.4 kernel repo & emenlow-noemgd BSP.

Nitin
Comment 2 Nitin Kamble 2013-01-29 06:05:26 UTC 
Gma500 does not work for tunnel creek, so it is not working from crownbay, and also will not work for fri2 & sys940x. But it is working for eMenlow. And it is enable for the emanloe-noemgd BSP now.