| Summary: | enable gma500 graphics support for intel-core2-32 BSP | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Nitin Kamble <nitin.a.kamble> |
| Component: | bsps-meta-intel | Assignee: | Saul Wold <sgw> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Lucian Musat <georgex.l.musat> |
| Severity: | normal | ||
| Priority: | Medium | CC: | alexandru.c.georgescu, ross.burton, sgw, tom.zanussi |
| Version: | 1.8 | ||
| Target Milestone: | 1.8 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| See Also: | http://bugzilla.yoctoproject.org/show_bug.cgi?id=7439 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | 6362 | ||
| Bug Blocks: | |||
|
Description
Nitin Kamble
2014-08-07 18:28:10 UTC
Assigning this to Max. I have an early draft of the patches for this here: http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=meliaser/3.14-meta-tunnelcreek-scc Still requires zarusd to be configured so that the gma500_gfx kernel module is disabled on FRI2. I am trying to push ImageConfigurator (in place of zaurusd) to enabling machine configuration for blacklisting of modules. So you can mention the need of blacklisting of the driver in the commit in detail, but it is not a blocker for you. (In reply to comment #3) > I am trying to push ImageConfigurator (in place of zaurusd) to enabling > machine configuration for blacklisting of modules. So you can mention the > need of blacklisting of the driver in the commit in detail, but it is not a > blocker for you. When you say it's not a blocker, should I actually submit a pull request for this, with the understanding that it will break intel-core2-32 on FRI2 until this is resolved? I have sent out the patch series for this. Handing this bug off to Nitin Kamble given my pending departure. This works if proper xorg.conf file is provided. The common BSP will support the emenlow completely with the GMA500 graphics when the machine-setup-tool parts is pull in. the machine setup tool will be upstreamed in the 1.8 m2 timeframe This has been fixed in the machinesetup tools commit. Once those commits are pulled in this bug can be closed. (In reply to comment #8) > This has been fixed in the machinesetup tools commit. Once those commits are > pulled in this bug can be closed. Hi Nitin, Any updates on this? So it looks like gma500-using hardware only needs a xorg.conf to set "SWCursor on". It's worth testing whether this bug in the kernel driver has since been fixed and the xorg.conf can be removed. This bug is fixed with the lastest kernel and xserver. While running xserver will generate an error in the Xorg.0.log reporting that psb or psb_drv is not found, this is not a problem since the modesetting driver will be used and is correct. This error can be ignored, it occurs since the out-sensing code is first looking for the psb or psb_drv modules. When an xorg.conf file exists and defines a Device this autosensing is skipped. |