From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 55336E00997; Tue, 28 Apr 2015 11:19:15 -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 C15DCE00932 for ; Tue, 28 Apr 2015 11:19:11 -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 0C23C6002647; Tue, 28 Apr 2015 21:19:10 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1430245150; bh=/TQ/cDrpEfqXCVH0F8WgKVWE+oiy7EftKVKqe48zE4g=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=eApgL9/UtIHvhW0xKtdBlFfNI3qVzoZ5nmmJDPiOX+ds6inuKaQ/EQ1xK5ILo6qfG gsqGeztBXG9TZrAwRmKEC+wP9xQyfvyc+Uib81tqJM7xenQ3eKpWhl7FzXKyL4cGtP AlPo7MgdWKu5etW0eCJMljsYAyDxVH28sE5ma3iU= Message-ID: <553FCF1D.30006@mail.bg> Date: Tue, 28 Apr 2015 21:19:09 +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: <1430109302-25721-1-git-send-email-picmaster@mail.bg> <553E5556.9070406@mail.bg> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-arm-extra][PATCH 1/2] linux-riotboard: Add separate riotboard kernel recipe 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: Tue, 28 Apr 2015 18:19:15 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Otavio, On 04/27/2015 07:26 PM, Otavio Salvador wrote: >>> I want to check with you if you really want to have a dedicated >>> recipe. For bugfixes (as now) you can use a bbappend as a temporary >>> solution and, at end of the day, easy to remove once this is fixed in >>> the kernel. >>> >>> Please let me know your thoughts... >> >> >> Do you mean something like this (bbappend in meta-fsl-arm-extra)? >> >> diff --git a/recipes-kernel/linux/linux-fslc_4.0.bbappend >> b/recipes-kernel/linux/linux-fslc_4.0.bbappend >> new file mode 100644 >> index 0000000..d7a4e72 >> --- /dev/null >> +++ b/recipes-kernel/linux/linux-fslc_4.0.bbappend >> @@ -0,0 +1,3 @@ >> +FILESEXTRAPATHS_append := ":${THISDIR}/${PN}" >> + >> +SRC_URI_imx6dl-riotboard = "file://riotboard-specific.patch" > > Yes. Just wanted to follow-up this technical topic. Even if considering that it's not of an urgent topic anymore, it would be good to have working path forward. The bbappend proposal above doesn't work. Here's my bbappend code (layer meta-fsl-arm-extra): diff --git a/recipes-kernel/linux/linux-fslc_4.0.bbappend b/recipes-kernel/linux/linux-fslc_4.0.bbappend new file mode 100644 index 0000000..4bf2349 --- /dev/null +++ b/recipes-kernel/linux/linux-fslc_4.0.bbappend @@ -0,0 +1,4 @@ +FILESEXTRAPATHS_append := ":${THISDIR}/${PN}-4.0" + +# Riotboard specific patch +SRC_URI_imx6dl-riotboard += "file://0001-Revert-mmc-sdhci-esdhc-imx-Call-mmc_of_parse.patch" This doesn't work out for reasons beyond my expertise: $ bitbake linux-fslc Loading cache: 100% |###########################################| ETA: 00:00:00 Loaded 2093 entries from dependency cache. NOTE: Error during finalise of /home/picmaster/work/yocto-master-riotboard/sources/meta-fsl-arm/recipes-kernel/linux/linux-fslc_4.0.bb ERROR: ExpansionError during parsing /home/picmaster/work/yocto-master-riotboard/sources/meta-fsl-arm/recipes-kernel/linux/linux-fslc_4.0.bb: Failure expanding variable S: ExpansionError: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: SRCREV was used yet no valid SCM was found in SRC_URI Summary: There was 1 ERROR message shown, returning a non-zero exit code. If I remove the board-specific suffix to SRC_URI, it doesn't generate the error message and works, but obviously doesn't achieve what I need. Any insight on this issue will be appreciated. Regards, Nikolay