[meta-freescale] [meta-fsl-arm-extra][PATCH 1/2] linux-riotboard: Add separate riotboard kernel recipe

[Nikolay Dimitrov]

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