Lines Matching refs:file
73 :term:`MACHINE` variable appropriately in your ``conf/local.conf`` file
116 ``bblayers.conf`` file as follows::
130 the build finishes, you can find the SDK installer file (i.e.
131 ``*.sh`` file) in the following directory::
135 For this example, the installer file is named
251 :term:`MACHINE` variable appropriately in your ``conf/local.conf`` file
293 ``bblayers.conf`` file as follows::
393 ``recipes-kernel`` directory holds your append file and eventual
397 ``meta-mylayer/conf`` directory and create the ``layer.conf`` file as
415 kernel's append file. This example uses the ``linux-yocto-4.12``
416 kernel. Thus, the name of the append file is
421 SRC_URI:append = " file://patch-file-one.patch"
422 SRC_URI:append = " file://patch-file-two.patch"
423 SRC_URI:append = " file://patch-file-three.patch"
442 - :ref:`kernel-dev/common:creating the append file`
456 You create this file in your custom layer. You also name it accordingly
459 the append file will typically be located as follows within your custom
466 The append file should initially extend the
487 As an example, consider the following append file used by the BSPs in
494 Here are the contents of this file. Be aware that the actual commit ID
496 strings in the file from the ``meta-yocto-bsp`` layer upstream.
523 This append file
525 Yocto Project. The file defines machines using the
530 machine name used by the Linux Yocto kernel. The file also uses the
537 append file points to specific commits in the
543 when developing a BSP, is the kernel configuration file (``.config``)
545 configuration file or a set of kernel configuration files that, when
547 accomplish this definition by putting the configurations in a file or a
549 kernel's append file and having the same name as the kernel's main
550 recipe file. With all these conditions met, simply reference those files
552 the append file.
554 For example, suppose you had some configuration options in a file called
555 ``network_configs.cfg``. You can place that file inside a directory
557 following to the append file. When the OpenEmbedded build system builds
561 SRC_URI += "file://network_configs.cfg"
567 the following in your append file::
569 SRC_URI += "file://myconfig.cfg \
570 file://eth.cfg \
571 file://gfx.cfg"
573 Another variable you can use in your kernel recipe append file is the
606 your ``.bbappend`` file as described in the previous section, and then
611 lines to your linux-yocto ``.bbappend`` file in your layer::
613 SRC_URI += "file://0001-first-change.patch"
614 SRC_URI += "file://0002-second-change.patch"
615 SRC_URI += "file://0003-third-change.patch"
632 file used for the eventual Linux kernel configuration by including a
633 ``defconfig`` file and by specifying configuration fragments in the
635 file.
637 If you have a complete, working Linux kernel ``.config`` file you want
638 to use for the configuration, as before, copy that file to the
640 directory, and rename the copied file to "defconfig". Then, add the
641 following lines to the linux-yocto ``.bbappend`` file in your layer::
644 SRC_URI += "file://defconfig"
647 for the file, while the
653 You can also use a regular ``defconfig`` file, as generated by the
655 task instead of a complete ``.config`` file. This only specifies the
658 in the linux-yocto ``.bbappend`` file in your layer::
665 file before applying any subsequent configuration fragments. The
667 the ``defconfig`` file and any configuration fragments you provide. You need
669 applies these on top of and after applying the existing ``defconfig`` file
675 console, create a file named ``8250.cfg`` in the ``${PN}`` directory
688 ``.bbappend`` file::
691 SRC_URI += "file://8250.cfg"
704 through a ``defconfig`` file that is pulled from the kernel source tree
709 SRC_URI += "file://defconfig"
717 ``defconfig`` file that is "in-tree".
719 To specify an "in-tree" ``defconfig`` file, use the following statement
726 and provides the path to the "in-tree" ``defconfig`` file to be used for
732 ``defconfig`` file, you need to be sure no files or statements set
733 :term:`SRC_URI` to use a ``defconfig`` other than your "in-tree" file (e.g.
734 a kernel's ``linux-``\ `machine`\ ``.inc`` file). In other words, if the
736 ``defconfig`` file, that statement will override your
763 ``calibrate.c`` source code file. Applying the patch and booting the
804 ``calibrate.c`` file::
808 2. *Edit the source file*: Edit the ``init/calibrate.c`` file to have
839 If the image you originally created resulted in a Wic file, you
871 your working directory to where you modified the ``calibrate.c`` file
880 commits as patches and create a ``.bbappend`` file, use the following
894 finishes, the patches and the ``.bbappend`` file are located in the
929 the kernel's ``calibrate.c`` source code file. Applying the patch and
940 section, use the following commands to edit the ``calibrate.c`` file:
945 ``calibrate.c`` file::
949 2. *Edit the source file*: Edit the ``calibrate.c`` file to have the
980 addition to your ``local.conf`` file specifying to use
991 …SRC_URI:pn-linux-yocto = "git:///path-to/linux-yocto-4.12;protocol=file;name=machine;branch=standa…
992 …git:///path-to/yocto-kernel-cache;protocol=file;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=…
1004 committed, and the ``local.conf`` file pointing to the kernel files,
1030 correctly, you can generate a ``*.patch`` file in the kernel source
1038 to pick up patches, you need to move the patch file you created in
1043 support patches. Before moving the patch file, you need to add
1052 hierarchy in your layer, you can move the patch file using the
1058 ``linux-yocto_4.12.bbappend`` file and insert statements that allow
1059 the OpenEmbedded build system to find the patch. The append file
1065 SRC_URI:append = "file://0001-calibrate.c-Added-some-printk-statements.patch"
1068 enable the OpenEmbedded build system to find the patch file.
1071 ":ref:`kernel-dev/common:creating the append file`" and
1094 ``.config`` file has all the right information in it for the image you
1096 fragments to make sure your ``.config`` file is just how you need it.
1097 You can also save known configurations in a ``defconfig`` file that the
1102 ``.config`` file to create the leanest kernel configuration file
1146 ``.config`` configuration file.
1150 You can use the entire ``.config`` file as the ``defconfig`` file. For
1153 ":ref:`kernel-dev/common:using an "in-tree" \`\`defconfig\`\` file`",
1154 and ":ref:`kernel-dev/common:creating a \`\`defconfig\`\` file`"
1174 Saving the selections updates the ``.config`` configuration file. This
1175 is the file that the OpenEmbedded build system uses to configure the
1176 kernel during the build. You can find and examine this file in the Build
1181 the ``.config`` file would be:
1195 Within the ``.config`` file, you can see the kernel settings. For
1205 as you want and save them, then compare the renamed configuration file
1206 against the newly created file. You can use the resulting differences as
1212 Be sure to make a copy of the ``.config`` file and do not just rename it.
1213 The build system needs an existing ``.config`` file from which to work.
1218 A ``defconfig`` file in the context of the Yocto Project is often a
1219 ``.config`` file that is copied from a build or a ``defconfig`` taken
1221 ``defconfig`` file to retain a known set of kernel configurations from
1223 ``.config`` file.
1228 file. The OpenEmbedded build system creates the final ``.config`` file used
1232 ``.config`` file. Copy that file to the appropriate
1235 file to "defconfig" (e.g.
1237 add the following lines to the linux-yocto ``.bbappend`` file in your
1241 SRC_URI += "file://defconfig"
1243 The :term:`SRC_URI` tells the build system how to search for the file, while the
1251 file before applying any subsequent configuration fragments. The
1253 the ``defconfig`` file and any configuration fragments you provide. You need
1255 applies these on top of and after applying the existing ``defconfig`` file
1264 Configuration fragments are simply kernel options that appear in a file
1267 configurations from a ``defconfig`` file. Thus, the final kernel
1269 ``defconfig`` file and then any configuration fragments you provide. The
1271 defconfig file configurations.
1274 appear in the ``.config`` file, which is in the :term:`Build Directory`.
1278 For more information about where the ``.config`` file is located, see the
1285 creates a configuration fragment file named ``my_smp.cfg`` that enables
1309 ``.config`` file from a known state. Because there are situations where
1318 to prepare a configuration fragment. The resulting file
1325 The ``diffconfig`` command creates a file that is a list of Linux kernel
1339 ``bblayers.conf`` file, which is located in your layer. The OpenEmbedded
1342 options in a file called ``myconfig.cfg``. If you put that file inside a
1344 the kernel's append file within your layer and then add the following
1345 statements to the kernel's append file, those configuration options will
1349 SRC_URI += "file://myconfig.cfg"
1355 :term:`SRC_URI` statement like the following in your append file::
1357 SRC_URI += "file://myconfig.cfg \
1358 file://eth.cfg \
1359 file://gfx.cfg"
1371 requested configuration does not appear in the final ``.config`` file or
1375 In order to run this task, you must have an existing ``.config`` file.
1377 information on how to create a configuration file.
1454 You can make sure the ``.config`` file is as lean or efficient as
1461 ``.config`` file against the input files. During the check, the task
1464 - Requested options that did not make the final ``.config`` file.
1481 For each output warning, a message points to the file that contains a
1490 successfully. Use this configuration file as your baseline.
1502 the final ``.config`` file.
1504 - Analyze and potentially drop values from the ``.config`` file that
1518 minimal, streamlined configuration file. Once you have the best
1527 easily managed in a text file, which allows for easy searches::
1531 Within the text file, you can see
1601 ``defconfig`` file or configuration fragment files in your layer.
1603 configuration. If you do not have a ``defconfig`` file, you can run
1609 resulting ``.config`` file to the ``files`` directory in your layer
1630 supported Git fetcher protocols (i.e. ``file``, ``git``, ``http``,
1632 a ``defconfig`` file or some configuration fragment files. The
1777 them appropriately for your machine configuration file:
1877 variable and by specifying the feature's ``.scc`` file path in the
1889 ``.scc`` file, which is relative to the root of the kernel Metadata. The
1897 When you specify the feature's ``.scc`` file on the :term:`SRC_URI`
1899 ``.scc`` file along with all its subdirectories to the kernel feature
1901 single ``.scc`` file in the :term:`SRC_URI` statement to reference multiple
1907 1. *Create the Feature File:* Create a ``.scc`` file and locate it just
1908 as you would any other patch file, ``.cfg`` file, or fetcher item you
1913 - You must add the directory of the ``.scc`` file to the
1915 ``.patch`` file.
1918 that contains the file you are adding. All subdirectories are
1922 adding has a ``test.scc`` file in the following directory::
1932 ``linux-yocto`` directory has both the feature ``test.scc`` file and
1933 a similarly named configuration fragment file ``test.cfg``.
1935 2. *Add the Feature File to SRC_URI:* Add the ``.scc`` file to the
1938 SRC_URI:append = " file://test.scc"
1956 file.