| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | concepts-appx.rst | 4 Advanced Kernel Concepts
7 Yocto Project Kernel Development and Maintenance
11 other kernels, are based off the Linux kernel releases from
12 https://www.kernel.org. At the beginning of a major Linux kernel
13 development cycle, the Yocto Project team chooses a Linux kernel based
15 final upstream ``kernel.org`` versions, and Yocto Project feature
16 requirements. Typically, the Linux kernel chosen is in the final stages
17 of development by the Linux community. In other words, the Linux kernel
20 team knows that the ``kernel.org`` final release will clearly be within
24 up-to-date Yocto Linux kernel possible, while still ensuring that the
[all …]
|
| H A D | intro.rst | 11 are you will work with the Linux kernel. This manual describes how to
12 set up your build host to support kernel development, introduces the
13 kernel development process, provides background information on the Yocto
14 Linux kernel :term:`Metadata`, describes
15 common tasks you can perform using the kernel tools, shows you how to
16 use the kernel Metadata needed to work with the kernel inside the Yocto
18 and maintains Yocto Linux kernel Git repositories and Metadata.
20 Each Yocto Project release has a set of Yocto Linux kernel recipes,
22 :yocto_git:`Source Repositories <>` under the "Yocto Linux Kernel"
23 heading. New recipes for the release track the latest Linux kernel
[all …]
|
| H A D | maint-appx.rst | 4 Kernel Maintenance
10 This section describes construction of the Yocto Project kernel source
12 Linux kernel repositories. These kernel repositories are found under the
13 heading "Yocto Linux Kernel" at :yocto_git:`/` and
18 divisions found in a Yocto Linux kernel. Thus, the Yocto Project Linux
19 kernel repository (or tree) and accompanying Metadata in the
20 ``yocto-kernel-cache`` are built.
23 particular Yocto Project Linux kernel repository and use it to build
27 in the Yocto Project Linux kernel in any clone of the Yocto Project
28 Linux kernel source repository and ``yocto-kernel-cache`` Git trees. For
[all …]
|
| H A D | advanced.rst | 4 Working with Advanced Metadata (``yocto-kernel-cache``)
11 Project kernel tools also support rich
16 BSPs and Linux kernel types.
18 Kernel Metadata exists in many places. One area in the
20 is the ``yocto-kernel-cache`` Git repository. You can find this repository
21 grouped under the "Yocto Linux Kernel" heading in the
24 Kernel development tools ("kern-tools") are also available in the Yocto Project
25 Source Repositories under the "Yocto Linux Kernel" heading in the
26 ``yocto-kernel-tools`` Git repository. The recipe that builds these
27 tools is ``meta/recipes-kernel/kern-tools/kern-tools-native_git.bb`` in
[all …]
|
| H A D | common.rst | 8 with the Yocto Project Linux kernel. These tasks include preparing your
9 host development system for kernel development, preparing a layer,
10 modifying an existing recipe, patching the kernel, configuring the
11 kernel, iterative development, working with your own sources, and
19 Preparing the Build Host to Work on the Kernel
22 Before you can do any kernel development, you need to be sure your build
41 Kernel development is best accomplished using
43 and not through traditional kernel workflow methods. The remainder of
49 Follow these steps to prepare to update the kernel image using
50 ``devtool``. Completing this procedure leaves you with a clean kernel
[all …]
|
| H A D | faq.rst | 4 Kernel Development FAQ
12 How do I use my own Linux kernel ``.config`` file?
16 ":ref:`kernel-dev/common:changing the configuration`"
23 ":ref:`kernel-dev/common:creating configuration fragments`"
26 How do I use my own Linux kernel sources?
30 ":ref:`kernel-dev/common:working with your own sources`"
33 How do I install/not-install the kernel image on the root filesystem?
36 The kernel image (e.g. ``vmlinuz``) is provided by the
37 ``kernel-image`` package. Image recipes depend on ``kernel-base``. To
38 specify whether or not the kernel image is installed in the generated
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-kernel/linux/ |
| H A D | linux-dummy.bb | 1 SUMMARY = "Dummy Linux kernel"
2 DESCRIPTION = "Dummy Linux kernel, to be selected as the preferred \
3 provider for virtual/kernel to satisfy dependencies for situations \
4 where you wish to build the kernel externally from the build system."
5 SECTION = "kernel"
10 PROVIDES += "virtual/kernel"
14 PACKAGES_DYNAMIC += "^kernel-module-.*"
15 PACKAGES_DYNAMIC += "^kernel-image-.*"
16 PACKAGES_DYNAMIC += "^kernel-firmware-.*"
18 PACKAGES += "kernel-modules kernel-vmlinux"
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-core/packagegroups/ |
| H A D | packagegroup-base.bb | 77 kernel-module-nls-utf8 \
78 kernel-module-input \
79 kernel-module-uinput \
80 kernel-module-rtc-dev \
81 kernel-module-rtc-proc \
82 kernel-module-rtc-sysfs \
83 kernel-module-unix"
156 kernel-module-msdos \
157 kernel-module-vfat \
158 kernel-module-nls-iso8859-1 \
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-filter/nftables/ |
| H A D | nftables_1.1.3.bb | 3 This software provides an in-kernel packet classification framework \
71 kernel-module-nft-chain-nat kernel-module-nft-queue \
72 kernel-module-nft-compat kernel-module-nft-quota \
73 kernel-module-nft-connlimit kernel-module-nft-redir \
74 kernel-module-nft-ct kernel-module-nft-reject \
75 kernel-module-nft-flow-offload kernel-module-nft-reject-inet \
76 kernel-module-nft-hash kernel-module-nft-reject-ipv4 \
77 kernel-module-nft-limit kernel-module-nft-reject-ipv6 \
78 kernel-module-nft-log kernel-module-nft-socket \
79 kernel-module-nft-masq kernel-module-nft-synproxy \
[all …]
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | kernel.its | 2 * Simple U-Boot uImage source file containing a single kernel
8 description = "Simple image with single Linux kernel";
12 kernel {
13 description = "Vanilla Linux kernel";
15 type = "kernel";
33 description = "Boot Linux kernel";
34 kernel = "kernel";
46 description = "Simple image with single Linux kernel on x86";
50 kernel {
51 description = "Vanilla Linux kernel";
[all …]
|
| H A D | howto.txt | 11 types (kernel, ramdisk, etc.), it also enhances integrity protection of images
20 git://git.kernel.org/pub/scm/utils/dtc/dtc.git
27 the uImage (kernel, ramdisk, etc.) is specified in the image source file in the
30 contains all the referenced data (kernel, ramdisk, etc.) and other information
69 Example 1 -- old-style (non-FDT) kernel booting
72 Consider a simple scenario, where a PPC Linux kernel built from sources on the
75 contains a gzip-compressed PPC Linux kernel (the only data file in this case).
77 doc/uImage.FIT/kernel.its (note that kernel.its assumes that vmlinux.bin.gz is
79 specified in the kernel.its file). Here's how to create the image and inspect
83 $ mkimage -f kernel.its kernel.itb
[all …]
|
| H A D | command_syntax_extensions.txt | 17 Linux kernel. The purpose of the following list is to document a complete list
20 Note: U-Boot supports two methods of booting a PowerPC Linux kernel: old way,
22 kernel is passed a pointer to the FDT. The boot method is indicated for each
51 Ad. 2. Boot kernel image located at <addr1>.
55 kernel and a ramdisk, respectively. The kernel is booted with initrd loaded
61 | (kernel, initrd) | (kernel, initrd, fdt) |
66 Ad. 4. Similar to case 3, but the kernel is booted without initrd. Second
70 Ad. 5. Boot kernel image located at <addr1> with initrd loaded with ramdisk
74 Ad. 6. <addr1> is the address of a kernel image, <addr2> is the address of a
75 ramdisk image, and <addr3> is the address of a FDT binary blob. Kernel is
[all …]
|
| H A D | overlay-fdt-boot.txt | 7 of similar boards and their expansion options. The same kernel on DT enabled
27 kernel {
29 type = "kernel";
70 kernel = "kernel";
74 kernel = "kernel";
78 kernel = "kernel";
82 kernel = "kernel";
86 kernel = "kernel";
90 kernel = "kernel";
114 being passed to the booting kernel. This saves on space and avoid the combinatorial
[all …]
|
| H A D | beaglebone_vboot.txt | 21 U-Boot has its device tree packaged wtih it, and the kernel's device tree is
22 packaged with the kernel. In particular this is important with verified boot,
26 everything verifies. On the other hand the kernel's device tree typically
27 changes when the kernel changes, so it is useful to package an updated device
28 tree with the kernel binary. U-Boot supports the latter with its flexible FIT
39 2. Obtain a suitable Linux kernel
42 kernel to be packaged, compressed and signed.
46 5. Sign the kernel
50 7. Put U-Boot and the kernel onto the board
59 this for U-Boot and also for the kernel if you build it. For example if you
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/manual/ |
| H A D | kernel-dev.json | 4 "@alias": "kernel-dev.kernel-dev.Kernel_dev_defconfig",
17 …"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki.…
18 …"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. http…
26 "@alias": "kernel-dev.kernel-dev.Kernel_dev_defconfig+fragments",
39 …"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki.…
40 …"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. http…
48 "@alias": "kernel-dev.kernel-dev.Kernel_dev_Applying_patches",
61 …"action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki.…
62 …"expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. http…
70 "@alias": "kernel-dev.kernel-dev.Kernel_dev_linux-yocto-local-source",
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/boot-wrapper-aarch64/ |
| H A D | boot-wrapper-aarch64_git.bb | 6 SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/mark/boot-wrapper-aarch64.git;branch=maste…
23 # by default use the standard kernel devicetree
25 # by the kernel.
29 # Kernel image to put in the image
33 # Kernel command line for the image
39 DEPENDS += "virtual/kernel dtc-native"
41 EXTRA_OECONF += "--with-kernel-dir=${WORKDIR}/kernel"
42 EXTRA_OECONF += "--with-dtb=${WORKDIR}/kernel/dummy.dtb"
46 # unset LDFLAGS solves this error when compiling kernel modules:
61 mkdir -p ${WORKDIR}/kernel/arch/arm64/boot
[all …]
|
| /openbmc/openbmc/poky/meta-skeleton/recipes-kernel/linux/ |
| H A D | linux-yocto-custom.bb | 1 SUMMARY = "An example kernel recipe that uses the linux-yocto and oe-core"
4 # kernel classes to apply a subset of yocto kernel management to git
5 # managed kernel repositories.
12 # You must also provide a Linux kernel configuration. The most direct
17 # To use the yocto kernel tooling to generate a BSP configuration
19 # yocto-kernel tools documentation.
41 # this, specify: KCONFIG_MODE="--alldefconfig" in the kernel
46 # example patch addition (for kernel v4.x only):
48 # example feature addition (for kernel v4.x only):
52 inherit kernel
[all …]
|
| /openbmc/qemu/scripts/ |
| H A D | update-syscalltbl.sh | 2 arch/alpha/kernel/syscalls/syscall.tbl,linux-user/alpha/syscall.tbl \
7 arch/m68k/kernel/syscalls/syscall.tbl,linux-user/m68k/syscall.tbl \
8 arch/microblaze/kernel/syscalls/syscall.tbl,linux-user/microblaze/syscall.tbl \
9 arch/mips/kernel/syscalls/syscall_n32.tbl,linux-user/mips64/syscall_n32.tbl \
10 arch/mips/kernel/syscalls/syscall_n64.tbl,linux-user/mips64/syscall_n64.tbl \
11 arch/mips/kernel/syscalls/syscall_o32.tbl,linux-user/mips/syscall_o32.tbl \
13 arch/parisc/kernel/syscalls/syscall.tbl,linux-user/hppa/syscall.tbl \
14 arch/powerpc/kernel/syscalls/syscall.tbl,linux-user/ppc/syscall.tbl \
16 arch/s390/kernel/syscalls/syscall.tbl,linux-user/s390x/syscall.tbl \
17 arch/sh/kernel/syscalls/syscall.tbl,linux-user/sh4/syscall.tbl \
[all …]
|
| /openbmc/u-boot/board/emulation/qemu-riscv/ |
| H A D | qemu-riscv.c | 31 debug("No chosen node found, can't get kernel start address\n"); in board_late_init()
36 ret = ofnode_read_u64(chosen_node, "riscv,kernel-start", in board_late_init()
39 ret = ofnode_read_u32(chosen_node, "riscv,kernel-start", in board_late_init()
43 debug("Can't find kernel start address in device tree\n"); in board_late_init()
53 * QEMU specifies the location of Linux (supplied with the -kernel argument)
54 * in the device tree using the riscv,kernel-start and riscv,kernel-end
57 * because BBL detects the kernel properties in the device tree and ignores
59 * kernel properties before booting Linux.
73 ret = fdt_setprop_u64(blob, chosen_offset, "riscv,kernel-start", 0); in ft_board_setup()
75 ret = fdt_setprop_u32(blob, chosen_offset, "riscv,kernel-start", 0); in ft_board_setup()
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.nokia_rx51 | 8 NOLO is expecting a kernel image and will treat any image it finds in
10 a kernel. In order to transparently boot the original kernel, it will be
16 the appended kernel image will be booted using some generated and some
23 but is disabled because it prevents the current Maemo kernel from booting.
30 * 0. if keyboard is closed boot automatically attached kernel image
33 * 3. try boot from attached kernel image
53 * run attachboot - Boot attached kernel image (attached to U-Boot binary)
57 * run kernload - Load kernel image ${mmckernfile}
59 * run kernboot - Boot loaded kernel image
60 * run kerninitrdboot - Boot loaded kernel image with loaded initrd image
[all …]
|
| H A D | mkimage.1 | 22 These images can contain the linux kernel, device tree blob, root file
30 format concatenates the individual parts (for example, kernel image,
177 Create legacy image with compressed PowerPC Linux kernel:
179 .B mkimage -A powerpc -O linux -T kernel -C gzip \\\\
184 Create FIT image with compressed PowerPC Linux kernel:
186 .B mkimage -f kernel.its kernel.itb
189 Create FIT image with compressed kernel and sign it with keys in the
193 .B mkimage -f kernel.its -k /public/signing-keys -K u-boot.dtb \\\\
195 .B -c """Kernel 3.8 image for production devices""" kernel.itb
206 .B -c """Kernel 3.8 image for production devices""" kernel.itb
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-kernel/lttng/lttng-tools/ |
| H A D | 0001-tests-add-check_skip_kernel_test-to-check-root-user-.patch | 5 lttng kernel modules
10 The current tests will run both userspace and kernel testing. Some of
12 device (e.g. userspace), so in this scenario, the kernel modules might
15 Add LTTNG_TOOLS_DISABLE_KERNEL_TESTS to skip the lttng kernel features
20 When this flag was set, all kernel related testcases would be marked as
38 tests/regression/kernel/test_all_events | 8 +----
39 tests/regression/kernel/test_callstack | 8 +----
40 tests/regression/kernel/test_channel | 8 +----
41 tests/regression/kernel/test_clock_override | 8 +----
42 tests/regression/kernel/test_event_basic | 8 +----
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-kernel/kexec/kexec-tools/ |
| H A D | kdump | 6 # 1. Load a kdump kernel image into memory;
40 #check whether kdump kernel image exists on the system
42 echo "No kdump kernel image found."
77 #check whether the running kernel supports kdump.
78 if [ ! -e /sys/kernel/kexec_crash_loaded ]; then
79 echo "Kdump isn't supported on the running kernel!!!"
80 ${LOGGER} "Kdump isn't supported on the running kernel!!!"
84 #check whether kdump kernel image has been loaded
85 rc=`cat /sys/kernel/kexec_crash_loaded`
92 #check the running kernel cmdline option,insure "crashkernel=" always set.
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-bsp/irda-utils/ |
| H A D | irda-utils_0.9.18.bb | 24 kernel-module-pxaficp-ir \
25 kernel-module-irda \
26 kernel-module-ircomm \
27 kernel-module-ircomm-tty \
28 kernel-module-irlan \
29 ${@bb.utils.contains('DISTRO_FEATURES', 'ppp', 'kernel-module-irnet', '',d)} \
30 kernel-module-irport \
31 kernel-module-irtty \
32 kernel-module-irtty-sir \
33 kernel-module-sir-dev \
[all …]
|
| /openbmc/openbmc/meta-security/recipes-kernel/lkrg/ |
| H A D | lkrg-module_0.9.7.bb | 1 SUMMARY = "Linux Kernel Runtime Guard"
3 kernel and detection of security vulnerability exploits against the kernel."
10 DEPENDS = "virtual/kernel elfutils"
18 inherit module kernel-module-split
27 sed -i -e 's/KERNEL/KERNEL_SRC/g' ${S}/Makefile
31 install -d ${D}${nonarch_base_libdir}/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
33 ${D}${nonarch_base_libdir}/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}/${MODULE_NAME}.ko
36 RPROVIDES:${PN} += "kernel-module-lkrg"
|