Hi Otavio,
On 04/30/2015 12:48 AM, Otavio Salvador wrote:
On Wed, Apr 29, 2015 at 6:42 PM, Gary Thomas <[email protected]> wrote:
On 2015-04-29 15:38, Nikolay Dimitrov wrote:
Several Yocto images fail to build because they're using packages that
require
imx6-specific hardware support (ASRC, VPU, GPU3D), which is not available
in
the mainline kernel. This patch fixes the following image builds:
- core-image-minimal
- core-image-base
- fsl-image-multimedia
Signed-off-by: Nikolay Dimitrov <[email protected]>
---
conf/machine/imx6dl-riotboard.conf | 3 +++
1 file changed, 3 insertions(+)
diff --git a/conf/machine/imx6dl-riotboard.conf
b/conf/machine/imx6dl-riotboard.conf
index b611ffb..05f6a38 100644
--- a/conf/machine/imx6dl-riotboard.conf
+++ b/conf/machine/imx6dl-riotboard.conf
@@ -15,3 +15,6 @@ PREFERRED_PROVIDER_virtual/kernel ?= "linux-fslc"
KERNEL_DEVICETREE = "imx6dl-riotboard.dtb"
SERIAL_CONSOLE = "115200 ttymxc1"
+
+MACHINE_EXTRA_RRECOMMENDS_remove = "fsl-alsa-plugins"
+MACHINE_GSTREAMER_PLUGIN_imx6dl-riotboard = ""
Is there some way to make this weaker? For example, these
changes will be icorrect if [when?] you get the linux-fslc 3.14
kernel going.
When he does this the forked 3.14 kernel will likely to become the
default one and those can be removed.
Not exactly. We're doing work to enable Yocto to work with linux-fslc,
and it would be unfair to throw this work on the junk. I would prefer
to see both mainline and fsl kernels being able to be used in a Yocto
build.
When I have some free time I will try to come up with a generic way to
'inform' the BSP about the kernel features and avoid those hacks.
This would be very welcome for cases like this. Thanks in advance for
helping out.
Regards,
Nikolay
--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
