Bruce Ashfield fcf53f6a8c yocto-cfg-fragments: introduce native provider of configuration fragments ... To allow the use of the yocto configuration fragments in scenarios where a kernel inherits kernel-yocto or has a custom fragment implementation, but doesn't directly include the yocto-kernel-cache in the kernel SRC_URI, we introduce a native provider of the fragments. This fragment provider is independent of a kernel tree and when added as a dependency to a recipe, the fragments will be placed in: recipe-sysroot-native/kcfg/ These can then be referenced on the SRC_URI or in KERNEL_FEEATURES by using '../recipe-sysroot-native/kcfg' as the relative path to the .scc or .cfg file. In the future, this won't be required as kernel-yocto will always check the native sysroot for fragments, and fragments will always be referenced by relative path from the base of the kernel-cache. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>		2021-10-13 22:45:55 -04:00
..
linux-yocto	k8s: update kernel configuration features	2021-07-29 10:59:59 -04:00
linux-%.bbappend	kernel: fix conditional application of fragments	2020-10-08 18:33:41 -04:00
linux-yocto_5.10_virtualization.inc	kernel: add 5.10 include file	2021-01-05 16:34:32 -05:00
linux-yocto_5.14_virtualization.inc	kernel: add 5.14 pattern	2021-09-22 13:40:28 -04:00
linux-yocto_virtualization.inc	global: overrides syntax conversion	2021-08-02 17:17:53 -04:00
linux-yocto-dev.bbappend	kernel: Add bbappend for linux-yocto-dev	2019-01-25 08:31:06 -05:00
yocto-cfg-fragments.bb	yocto-cfg-fragments: introduce native provider of configuration fragments	2021-10-13 22:45:55 -04:00