[yocto] SRC_URI scope and kernel fragments in non-yocto kernel recipes

[stephen.lawrence at renesas.com]

Hi,

I'm wondering if SRC_URI has some limitations as to where it will be 
expanded.

I have a bsp with 2 kernel recipes. One for mainline, the other for the 
yocto kernel.
The kernel may be used with some middleware that requires some further 
patches and kernel configuration.
I hoped to isolate these into a separate file that could be easily 
commented in or out from the kernel bb file.
This file would have a SRC_URI += for the patches and a kernel fragment 
.cfg, e.g:
# Add some m/w patches
SRC_URI += " file://some.patch"

# Add some m/w kernel req
SRC_URI += " file://mw-kernel-config.cfg"

I first tried following the bsp tooling example and placed this within a 
scc file but the SRC_URI wasn't picked up.
I most recently tried placing it in an include but had the same result.

I finally tried adding two SRC_URIs directly into the kernel recipe.
The one listing the patches was applied. The one listing the kernel 
fragment was not.

I suspect the kernel fragment issue is down to the fact that a yocto 
kernel recipe is not being used,
i.e. it relies on the yocto kernel meta data mechanism?

Why is the SRC_URI containing the additional patches applied when 
referenced directly in the bb file,
but not when referenced in an include or scc file?

I suspect this has come up before, but I can't find anything in the doc or 
list archives.

I'm using the poky master branch rev 
93c04c16e45a3c8f60f8ffc0b26a78c24bda71da

Thanks for any suggestions. My aim is to get to a point I can upstream the 
bsp.

Cheers

Steve


Stephen  Lawrence, Senior Engineer, Systems, Linux/SDK, Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, SL8 5FH, Bourne End, UK,  Phone:+44 1628 651-789, Fax:+44 1628 651-804, mailto:Stephen.Lawrence at renesas.com, http://www.renesas.eu

This message is intended only for the use of the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient, you are hereby notified that any dissemination of this email (including any attachments thereto) is strictly prohibited. If you have received this email in error, please notify the sender immediately by telephone or email  and permanently destroy the original without making any copy. Please note that any material and advice from this mail is provided free of charge and shall be used as an example for demonstration purposes only. 
RENESAS MAKES NO WARRANTIES THAT THE USAGE OF INFORMATION OR ADVICE FROM THIS E-MAIL WILL NOT INFRINGE ANY INTELLECTUAL PROPERTY RIGHTS (E.G. PATENTS, COPYRIGHTS). RENESAS CANNOT GUARANTEE BUG FREE OPERATION AND THE RECIPIENT WILL USE AND/OR DISTRIBUTE IT ONLY AT HIS OWN RISK. IN NO EVENT SHALL RENESAS BE LIABLE FOR ANY DAMAGE.  The communication with Renesas Electronics Europe Ltd does not amend any written agreement in place. 
 
Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK.  Registered in England & Wales under Registered No. 04586709.