From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 9E303E0088A; Thu, 19 Feb 2015 08:00:22 -0800 (PST) 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 F2317E008D4 for ; Thu, 19 Feb 2015 08:00:04 -0800 (PST) Received: from [192.168.0.123] (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 8442F60004EF; Thu, 19 Feb 2015 18:00:03 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1424361603; bh=0bniNiInD5/fpJPZ0WA0fBpqoLn+aOExsptcgZUg1pA=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Y/r+0hqsYSaN+gfsltNSJ2NCilnQfgH2dEecSkx7LO0bN5FB+AT+SL0cQoNCxsqTg x3jrJNx+2n4Ccqrl7RIJDmdqok2lRfxgSyxv3XnhnQiVNKgs9kR3YhCLL3q1LgSSat TGu/QQ8pDcZ0oIOF91dSg5128I4wGZJh6Fe0tFDE= Message-ID: <54E60883.6010609@mail.bg> Date: Thu, 19 Feb 2015 18:00:03 +0200 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0 MIME-Version: 1.0 To: Wally Yeh References: <20150213225850.E064F1CBCF408@nano.lab.ossystems.com.br> <54DF80F4.3060001@mail.bg> <54E09EF9.1010902@mail.bg> <54E4DB34.2000901@mail.bg> <54E606AD.7090101@mail.bg> In-Reply-To: <54E606AD.7090101@mail.bg> Cc: meta-freescale , Otavio Salvador Subject: Re: Updates to meta-fsl-arm (dizzy) in 2015-02-13 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: Thu, 19 Feb 2015 16:00:22 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Wally, On 02/19/2015 05:52 PM, Nikolay Dimitrov wrote: > Hi Wally, > > On 02/19/2015 04:37 PM, Wally Yeh wrote: >> Hi, Otavio: >> I just build a fresh yocto dizzy on my parent's computer, and >> found there's no Nikolay V2 patch on linux-imx. where could I get it? >> the V1 patch I get is from Nikolay's meta-freescale thread: >> >> https://lists.yoctoproject.org/pipermail/meta-freescale/2015-February/012718.html >> > > Please check with "repo info" that you're using "dizzy", and then do > "repo sync". Then verify that the following patch is available: > > sources/meta-fsl-arm/recipes-kernel/linux/linux-imx-3.10.17/0002-ARM-imx6sl-Disable-imx6sl-specific-code-when-imx6sl-.patch > > > Also, this recipe... > > sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb > > ...should contain the text: > > SRC_URI += > "file://0001-ARM-clk-imx6q-fix-video-divider-for-revision-1.0-of-.patch \ > > file://0002-ARM-imx6sl-Disable-imx6sl-specific-code-when-imx6sl-.patch \ > " > > If you're building kernel 3.10.17, there is zero chance for this to not > work. There's one case when these patches won't be applied to your kernel - it's when you're working on a custom board and you're using your own recipe for building FSL kernel 3.10.17. You can solve this by: 1. Place your kernel recipe in meta-fsl-arm/recipes-kernel/linux alongside the Freescale's ones (not cool, but works) 2. Copy the patches in your custom layer and enable them in your SRC_URI var (much better) Kind regards, Nikolay