| Summary: | core-image-lsb-sdk image build for crownbay BSP fails on emgd install | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Nitin Kamble <nitin.a.kamble> |
| Component: | bsps-meta-intel | Assignee: | Nitin Kamble <nitin.a.kamble> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Medium+ | CC: | dvhart, richard.purdie, sgw, tom.zanussi |
| Version: | 1.4 | ||
| Target Milestone: | 1.4 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Nitin Kamble
2013-01-22 20:01:24 UTC
In the initial investigation I have found that the XSERVER var is not empty for the core-image-lsb-sdk image. There is logic in the EMGD based BSP configurations to disable emgd components which depend on X if the XSERVER var does not include emgd driver. Now the XSERVER var is valid and includes the emgd driver, that logic is not anymore working to block the emgd VA components going into the image. I need to find a new solution to block the emgd VA components getting into LSB image, and I don't see any obvious solution to this issue. One solution can be we can make XSERVER var empty for all the LSB images. But that would need approval from RP. Same issue for emenlow BSP (all the EMGD based BSPs) as well: http://autobuilder.yoctoproject.org:8010/builders/emenlow/builds/241/steps/shell_60/logs/stdio Darren, We probably can fix this issue by extending the LSB image recipes in the meta-intel layer. The extention will be addition of this line XSERVER = "" I think this issue is for meta-intel BSPs because we have the VA support in there, so it kind of makes sense to fix them inside meta-intel only. Thanks, Nitin RP & I have a solution for this now. I am testing the changes. Commits to fix went into oecore & meta-intel. meta-intel: commit f3bccf8f0c91b4edff480327895dff5efb792f82 Author: Nitin A Kamble <nitin.a.kamble@intel.com> Date: Wed Jan 23 15:30:08 2013 -0800 crownbay.conf: use the new method for specifying VA codecs This replaces the old VA_FEATURES method to specify the codecs. These VA codecs are included in the image when image has 'hwcodec' in the IMAGE_FEATURES. And one can disable the VA features by redefining the IMAGE_FEATURES var in the local.conf . The gst-va-intel package pulls in emgd driver and x11 pieces, hence it is moved to the XSERVERCODECS var. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> oe-core: commit f19bdeab37e8433c42a36383c78b0f10e700342d Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Wed Jan 23 21:56:11 2013 -0800 core-image: Add hwcodecs IMAGE_FEATURE Currently hardware codecs are being injected in rather ugly ways and end up either in no or all images. This adds a dedicated IMAGE_FEATURE for them based on the MACHINE_HWCODECS variable. We may need to refine this in due course but this patch at least illustrates the concept. (From OE-Core rev: 1cb370587fd72e3f0f69678748108cc4116767fb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> commit b064818003db3d3a3a18a4a27786725b28bd8d56 Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Wed Jan 23 21:56:09 2013 -0800 packagegroup-core-x11-xserver: Add XSERVERCODECS variable At present its hard for the system to provide extra x11 hardware codecs. We could lump them in with the XSERVER variable but this is suboptimal as in some use cases the user might not want to include them in some images. With this patch we keep our options open about separating usage of the two in the future. (From OE-Core rev: 285c7577813cf75a3b554f8a5d6d7ba002127ef4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |