From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 05A00E0098D; Wed, 29 Apr 2015 15:12:50 -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 93BECE007CC for ; Wed, 29 Apr 2015 15:12:46 -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 EDA1F6001A22; Thu, 30 Apr 2015 01:12:44 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1430345565; bh=T2vtfXerTXBWWdZHbL1lScbqLR1Pw5T6qIElQf9oWIc=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Rz4yCAzRnesP4halkKGRNGR1XONsVGY17CNZ1KtPwMXIGg+ShFc846UCSWDjQg5LB IDMPJTaocalktxakN/KmOcRTvfxjTohjNLAVGSEeDuiNow3JKEteNUVqlwrrMJ05D/ KgcRxenSEAsH0dzlpX9WMu09ruKuE7TDiqF57l94= Message-ID: <5541575C.4030409@mail.bg> Date: Thu, 30 Apr 2015 01:12:44 +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: Gary Thomas References: <1430343511-14563-1-git-send-email-picmaster@mail.bg> <55415041.1020508@mlbassoc.com> <55415253.8010108@mail.bg> <554153A9.8030404@mlbassoc.com> In-Reply-To: <554153A9.8030404@mlbassoc.com> Cc: meta-freescale@yoctoproject.org 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 22:12:50 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Gary, On 04/30/2015 12:56 AM, Gary Thomas wrote: > On 2015-04-29 15:51, Nikolay Dimitrov wrote: >> Hi Gary, >> >> On 04/30/2015 12:42 AM, 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. >> >> Yes, I was also thinking about it. My plan is to fix this when >> introducing the 3.14 support, but as of today there's no such support >> for riotboard, so I would prefer to push whatever I have >> working. > > I've not looked at backporting to 3.14 (I was leaving that for you!) > but how different would the device tree from 4.1-rc1 need to be to > work with 3.14? Isn't that (plus the stitching to get it built) > about all that's needed? I don't expect any back-porting work for FSL 3.14.28 kernel, only DT work. My last experience of playing with DTs on several imx6 dual/quad customer boards showed that beyond the initial enthusiasm it always took much more than initially estimated, sometimes up to 2-3 days work. I don't like to say that, but for most of us Yocto is a spare-time effort, which means its priority is below the commercial projects we're working on. But I can assure you that I would love to see 3.14.28 running on riotboard, just as you, and I'll do my best to make it happen. If you feel enthusiastic about helping out with enabling the 3.14.28 kernel support, your help will be warmly appreciated. Regards, Nikolay