documentation/kernel-dev/advanced.rst

13 complex policies and Board Support Package (BSP) support. The purpose of
37 definitions in linux-yocto recipes for corresponding BSPs. A BSP
39 hardware-specific features. The BSP can be influenced from within the
55 using the same BSP description. Multiple Corei7-based BSPs could share
58 is the machine type within a BSP Layer. Even with this distinction,
92 During the build, the kern-tools search for the BSP description file
94 variables passed in from the recipe. The tools use the first BSP
443    file. The Board Support Package (BSP) file can implicitly define the
448 BSP Descriptions
451 BSP descriptions (i.e. ``*.scc`` files) combine kernel types with
453 defined independently in the BSP layer, and then aggregated with each
458    For BSPs supported by the Yocto Project, the BSP description files
463 This section overviews the BSP description structure, the aggregation
464 concepts, and presents a detailed example using a BSP supported by the
465 Yocto Project (i.e. BeagleBone Board). For complete information on BSP
471 For simplicity, consider the following root BSP layer description files
479 BSP filenames for the BeagleBone Board BSP, which is supported by the
485 Each file uses the root name (i.e "beaglebone") BSP name followed by the
503 Every top-level BSP description file
517 variable in the kernel recipe and the :term:`KTYPE` variable in the BSP
567 BSP descriptions can aggregate features. Consider the Minnow BSP
574    Although the Minnow Board BSP is unused, the Metadata remains and is
601 fragment (``minnow.cfg``) specific to the Minnow BSP as well as several
635 that defines all enabled hardware for the BSP that is common to all
701 in recipe-space within a BSP layer::
722 If the BSP description is in recipe space, you cannot simply list the
783    patches in the BSP descriptions of the applicable boards.
789    merging that branch into your BSP when needed.
802 description, you simply include that into the BSP description as
805 You can find information on how to create patches and BSP descriptions
826 Another method is to use the ``branch`` command in the BSP
878 To merge a feature branch into a BSP, insert the ``git merge`` command