diff options
| author |   Bruce Ashfield <bruce.ashfield@gmail.com> | 2019-12-29 22:07:21 -0500 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2019-12-30 23:38:12 +0000 |
| commit | 747ad3ca1e987668c8ed444cfc595d751bc0d0b2 (patch) | |
| tree | b87588748764f57b0e30a6850bff89d375443b72 /meta/classes/linuxloader.bbclass | |
| parent | b538fedff2cbd4604a7c73fdee07167f1ad3155a (diff) | |
| download | openembedded-core-contrib-747ad3ca1e987668c8ed444cfc595d751bc0d0b2.tar.gz | |
kernel-yocto: allow external (aka non-integrated) BSPs to supply patches
By default, only explicitly specified .scc files or patches are applied
to a BSP as part of the patching phase. This allows the reference BSPs
to be integrated into a kernel tree, and use the same meta data for tree
generation and for runtime building. It also greatly simplies the
processing of kernel meta data.
That being said, if an external (and fully standalone) kmeta repository
is used, it very well may contain both patches and configuration. To
allow the BSP definition to supply patches and config, we introduce a
new kernel meta data definition:
define KMETA_EXTERNAL_BSP t
This can be set in any .scc file that wants to specify both patches
and configuration.
If specifying this per-BSP is not desired, a secondary variable is
used:
KMETA_EXTERNAL_BSPS
When that is set in a bbappend, any located BSP definitions will be used
for both patches and configuration.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/linuxloader.bbclass')
0 files changed, 0 insertions, 0 deletions