documentation/kernel-dev/advanced.rst

108 feature specified as "features/netfilter/netfilter.scc", specify::
110    KERNEL_FEATURES += "features/netfilter/netfilter.scc"
113 feature called "cfg/sound.scc" just for the ``qemux86`` machine,
116    KERNEL_FEATURES:append:qemux86 = " cfg/sound.scc"
129 The kernel Metadata consists of three primary types of files: ``scc``
131 ``scc`` files define variables and include or otherwise reference any of
137 The ``scc`` description files are used to define two fundamental types
170 Use these guidelines to help place your ``scc`` description files within
204    ``scc`` stands for Series Configuration Control, but the naming has
206    it had in the past. Consider ``scc`` files to be description files.
213 parameters in a configuration fragment file (``.cfg``) and a ``.scc``
219 two files: ``smp.scc`` and ``smp.cfg``. You can find these files in the
223    cfg/smp.scc:
243 Within the ``smp.scc`` file, the
248 Also within the ``smp.scc`` file, the ``kconf`` command includes the
249 actual configuration fragment in an ``.scc`` file, and the "hardware"
279 ``build.scc`` and a set of ``*.patch`` files. You can find these files
283 The following listings show the ``build.scc`` file and part of the
286    patches/build/build.scc:
316 patch. In the example ``build.scc`` file, there are five patch statements
332    features/myfeature.scc
338       include cfg/myfeature_dependency.scc
402 For any given kernel type, the Metadata is defined by the ``.scc`` (e.g.
403 ``standard.scc``). Here is a partial listing for the ``standard.scc``
412    #             include ktypes/standard/standard.scc nocfg
414    #             include ktypes/standard/standard.scc nocfg inherit
418    include ktypes/base/base.scc
423    include features/kgdb/kgdb.scc
428    include cfg/net/ip6_nf.scc
429    include cfg/net/bridge.scc
431    include cfg/systemd.scc
433    include features/rfkill/rfkill.scc
435 As with any ``.scc`` file, a kernel type definition can aggregate other
436 ``.scc`` files with ``include`` commands. These definitions can also
442    It is not strictly necessary to create a kernel type ``.scc``
451 BSP descriptions (i.e. ``*.scc`` files) combine kernel types with
476    bsp_root_name-kernel_type.scc
482    beaglebone-standard.scc
483    beaglebone-preempt-rt.scc
488 Examine the ``beaglebone-standard.scc`` file::
494    include ktypes/standard/standard.scc
497    include beaglebone.scc
500    include features/latencytop/latencytop.scc
501    include features/profiling/profiling.scc
524    include ktypes/standard/standard.scc
534    include mybsp.scc
538    include beaglebone.scc
544 are not in a ``*.scc`` file, you can include them as follows::
550 ("mti-malta32"). Here is the ``mti-malta32-le-standard.scc`` file::
557    include ktypes/standard/standard.scc
560    include mti-malta32.scc
566 Many real-world examples are more complex. Like any other ``.scc`` file,
570 ``yocto-kernel-cache/bsp/minnow/minnow.scc``):
579    include cfg/x86.scc
580    include features/eg20t/eg20t.scc
581    include cfg/dmaengine.scc
582    include features/power/intel.scc
583    include cfg/efi.scc
584    include features/usb/ehci-hcd.scc
585    include features/usb/ohci-hcd.scc
586    include features/usb/usb-gadgets.scc
587    include features/usb/touchscreen-composite.scc
588    include cfg/timer/hpet.scc
589    include features/leds/leds.scc
590    include features/spi/spidev.scc
591    include features/i2c/i2cdev.scc
592    include features/mei/mei-txe.scc
600 The ``minnow.scc`` description file includes a hardware configuration
603 found on the machine. This ``minnow.scc`` description file is then
607 ``minnow-standard.scc``)::
615    include minnow.scc
617    # Extra minnow configs above the minimal defined in minnow.scc
618    include cfg/efi-ext.scc
619    include features/media/media-all.scc
620    include features/sound/snd_hda_intel.scc
622    # The following should really be in standard.scc
624    include cfg/usb-mass-storage.scc
625    include cfg/boot-live.scc
628    include features/latencytop/latencytop.scc
629    include features/profiling/profiling.scc
631    # Requested drivers that don't have an existing scc
634 The ``include`` command midway through the file includes the ``minnow.scc`` description
639 ``minnow-tiny.scc``)::
647    include minnow.scc
707                |-- bsp-standard.scc
714 specify the ``.scc`` files on the
716 and fetches any files referenced in the ``.scc`` files by the
723 ``*.scc`` in the :term:`SRC_URI` statement. You need to use the following
829    mybsp.scc:
833       include standard.scc
837       include mybsp-hw.scc
881    mybsp.scc:
885       include standard.scc
890       include mybsp-hw.scc
896 within an SCC description file (``.scc``):