From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 97533E00998; Wed, 29 Apr 2015 14:55:26 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3AA24E007CC for ; Wed, 29 Apr 2015 14:55:24 -0700 (PDT) Received: from [192.168.0.62] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id A13C56001EA0; Thu, 30 Apr 2015 00:55:23 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1430344523; bh=HriEY81p5CkWSKs8KKdCpfGuN4nyBmqMqAOUyPCL9N8=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=TqRCNuA3C6I6ARLNR785tuaz/kvgtGUIb382cgJY9AQ67342OZjVSmgA/NPOkybsy IR/gybifFPa5XdSXEF6xkTjY4tR0L1WMj1fnZ4z1uBYQExUt29gQKOJDv9SoFrHaBL BwUnVPyD7bDA0BjWL6M50uEtyd9lYUX8FZmcf7o0= Message-ID: <5541534B.5050000@mail.bg> Date: Thu, 30 Apr 2015 00:55:23 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Otavio Salvador References: <1430343511-14563-1-git-send-email-picmaster@mail.bg> <55415041.1020508@mlbassoc.com> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" , Gary Thomas Subject: Re: [meta-fsl-arm-extra][PATCH v2] riotboard: Fix broken image builds against linux-fslc X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2015 21:55:26 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Otavio, On 04/30/2015 12:48 AM, Otavio Salvador wrote: > On Wed, Apr 29, 2015 at 6:42 PM, Gary Thomas 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 >>> --- >>> 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