| /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 | 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 | 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 | 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 …]
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | kernel-api.rst | 2 The Linux Kernel API
9 .. kernel-doc:: include/linux/list.h
24 .. kernel-doc:: lib/vsprintf.c
27 .. kernel-doc:: include/linux/kstrtox.h
30 .. kernel-doc:: lib/kstrtox.c
33 .. kernel-doc:: lib/string_helpers.c
39 .. kernel-doc:: include/linux/fortify-string.h
42 .. kernel-doc:: lib/string.c
45 .. kernel-doc:: include/linux/string.h
48 .. kernel-doc:: mm/util.c
[all …]
|
| H A D | mm-api.rst | 8 .. kernel-doc:: arch/x86/include/asm/uaccess.h
11 .. kernel-doc:: arch/x86/lib/usercopy_32.c
14 .. kernel-doc:: mm/gup.c
22 .. kernel-doc:: include/linux/gfp_types.h
25 .. kernel-doc:: include/linux/gfp_types.h
28 .. kernel-doc:: include/linux/gfp_types.h
31 .. kernel-doc:: include/linux/gfp_types.h
37 .. kernel-doc:: include/linux/slab.h
40 .. kernel-doc:: mm/slab.c
43 .. kernel-doc:: mm/slab_common.c
[all …]
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | basics.rst | 7 .. kernel-doc:: include/linux/module.h
13 .. kernel-doc:: include/linux/mod_devicetable.h
21 .. kernel-doc:: include/linux/sched.h
24 .. kernel-doc:: kernel/sched/core.c
27 .. kernel-doc:: kernel/sched/cpupri.c
30 .. kernel-doc:: kernel/sched/fair.c
33 .. kernel-doc:: include/linux/completion.h
39 .. kernel-doc:: include/linux/jiffies.h
42 .. kernel-doc:: kernel/time/time.c
45 .. kernel-doc:: kernel/time/timer.c
[all …]
|
| H A D | infrastructure.rst | 7 .. kernel-doc:: include/linux/device.h
11 .. kernel-doc:: include/linux/device/bus.h
14 .. kernel-doc:: include/linux/device/class.h
17 .. kernel-doc:: include/linux/device/driver.h
23 .. kernel-doc:: drivers/base/init.c
26 .. kernel-doc:: include/linux/device/driver.h
29 .. kernel-doc:: drivers/base/driver.c
32 .. kernel-doc:: drivers/base/core.c
35 .. kernel-doc:: drivers/base/syscore.c
38 .. kernel-doc:: include/linux/device/class.h
[all …]
|
| /openbmc/linux/Documentation/admin-guide/kdump/ |
| H A D | kdump.rst | 11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
12 dump of the system kernel's memory needs to be taken (for example, when
13 the system panics). The system kernel's memory image is preserved across
14 the reboot and is accessible to the dump-capture kernel.
23 When the system kernel boots, it reserves a small section of memory for
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
30 regardless of where the kernel loads. For simpler handling, the whole
31 low 1M is reserved to avoid any later kernel or device driver writing
[all …]
|
| /openbmc/linux/scripts/ |
| H A D | head-object-list.txt | 14 arch/alpha/kernel/head.o
15 arch/arc/kernel/head.o
16 arch/arm/kernel/head-nommu.o
17 arch/arm/kernel/head.o
18 arch/csky/kernel/head.o
19 arch/hexagon/kernel/head.o
20 arch/ia64/kernel/head.o
21 arch/loongarch/kernel/head.o
24 arch/m68k/kernel/head.o
25 arch/m68k/kernel/sun3-head.o
[all …]
|
| /openbmc/linux/arch/arm/ |
| H A D | Kconfig.debug | 7 bool "Export kernel pagetable layout to userspace via debugfs"
13 Say Y here if you want to show the kernel pagetable layout in a
14 debugfs file. This information is only useful for kernel developers
15 who are working in architecture specific areas of the kernel.
17 kernel.
27 This is useful for discovering cases where the kernel is leaving
38 Note that even if the check fails, your kernel is possibly
41 of other unfixed kernel bugs easier.
44 once the kernel has booted up - it's a one time check.
49 prompt "Choose kernel unwinder"
[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/linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-mm-damon | 1 what: /sys/kernel/mm/damon/
3 Contact: SeongJae Park <sj@kernel.org>
8 What: /sys/kernel/mm/damon/admin/
10 Contact: SeongJae Park <sj@kernel.org>
14 What: /sys/kernel/mm/damon/admin/kdamonds/nr_kdamonds
16 Contact: SeongJae Park <sj@kernel.org>
21 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/state
23 Contact: SeongJae Park <sj@kernel.org>
37 What: /sys/kernel/mm/damon/admin/kdamonds/<K>/pid
39 Contact: SeongJae Park <sj@kernel.org>
[all …]
|
| H A D | debugfs-driver-habanalabs | 1 What: /sys/kernel/debug/habanalabs/hl<n>/addr
4 Contact: ogabbay@kernel.org
11 What: /sys/kernel/debug/habanalabs/hl<n>/clk_gate
14 Contact: ogabbay@kernel.org
17 What: /sys/kernel/debug/habanalabs/hl<n>/command_buffers
20 Contact: ogabbay@kernel.org
24 What: /sys/kernel/debug/habanalabs/hl<n>/command_submission
27 Contact: ogabbay@kernel.org
31 What: /sys/kernel/debug/habanalabs/hl<n>/command_submission_jobs
34 Contact: ogabbay@kernel.org
[all …]
|
| H A D | debugfs-hisi-hpre | 1 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs
3 Contact: linux-crypto@vger.kernel.org
7 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl
9 Contact: linux-crypto@vger.kernel.org
14 What: /sys/kernel/debug/hisi_hpre/<bdf>/rdclr_en
16 Contact: linux-crypto@vger.kernel.org
23 What: /sys/kernel/debug/hisi_hpre/<bdf>/current_qm
25 Contact: linux-crypto@vger.kernel.org
30 What: /sys/kernel/debug/hisi_hpre/<bdf>/alg_qos
32 Contact: linux-crypto@vger.kernel.org
[all …]
|
| H A D | debugfs-hisi-sec | 1 What: /sys/kernel/debug/hisi_sec2/<bdf>/clear_enable
3 Contact: linux-crypto@vger.kernel.org
9 What: /sys/kernel/debug/hisi_sec2/<bdf>/current_qm
11 Contact: linux-crypto@vger.kernel.org
17 What: /sys/kernel/debug/hisi_sec2/<bdf>/alg_qos
19 Contact: linux-crypto@vger.kernel.org
27 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/qm_regs
29 Contact: linux-crypto@vger.kernel.org
34 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/current_q
36 Contact: linux-crypto@vger.kernel.org
[all …]
|
| H A D | debugfs-hisi-zip | 1 What: /sys/kernel/debug/hisi_zip/<bdf>/comp_core[01]/regs
3 Contact: linux-crypto@vger.kernel.org
7 What: /sys/kernel/debug/hisi_zip/<bdf>/decomp_core[0-5]/regs
9 Contact: linux-crypto@vger.kernel.org
13 What: /sys/kernel/debug/hisi_zip/<bdf>/clear_enable
15 Contact: linux-crypto@vger.kernel.org
22 What: /sys/kernel/debug/hisi_zip/<bdf>/current_qm
24 Contact: linux-crypto@vger.kernel.org
29 What: /sys/kernel/debug/hisi_zip/<bdf>/alg_qos
31 Contact: linux-crypto@vger.kernel.org
[all …]
|
| /openbmc/linux/Documentation/networking/ |
| H A D | kapi.rst | 11 .. kernel-doc:: include/linux/net.h
17 .. kernel-doc:: include/linux/skbuff.h
20 .. kernel-doc:: include/net/sock.h
23 .. kernel-doc:: net/socket.c
26 .. kernel-doc:: net/core/skbuff.c
29 .. kernel-doc:: net/core/sock.c
32 .. kernel-doc:: net/core/datagram.c
35 .. kernel-doc:: net/core/stream.c
41 .. kernel-doc:: net/core/filter.c
47 .. kernel-doc:: include/uapi/linux/gen_stats.h
[all …]
|
| /openbmc/linux/Documentation/gpu/ |
| H A D | drm-kms-helpers.rst | 7 userspace requests to kernel internal objects. Everything else is handled by a
39 .. kernel-doc:: include/drm/drm_modeset_helper_vtables.h
42 .. kernel-doc:: include/drm/drm_modeset_helper_vtables.h
53 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
59 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
65 .. kernel-doc:: include/drm/drm_atomic_helper.h
68 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
74 .. kernel-doc:: drivers/gpu/drm/drm_atomic_state_helper.c
80 .. kernel-doc:: drivers/gpu/drm/drm_atomic_state_helper.c
86 .. kernel-doc:: drivers/gpu/drm/drm_gem_atomic_helper.c
[all …]
|
| /openbmc/linux/Documentation/sound/kernel-api/ |
| H A D | alsa-driver-api.rst | 10 .. kernel-doc:: sound/core/init.c
14 .. kernel-doc:: sound/core/device.c
18 .. kernel-doc:: sound/core/sound.c
22 .. kernel-doc:: sound/core/memory.c
23 .. kernel-doc:: sound/core/memalloc.c
31 .. kernel-doc:: sound/core/pcm.c
32 .. kernel-doc:: sound/core/pcm_lib.c
33 .. kernel-doc:: sound/core/pcm_native.c
34 .. kernel-doc:: include/sound/pcm.h
38 .. kernel-doc:: sound/core/pcm_misc.c
[all …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | api-summary.rst | 14 .. kernel-doc:: include/linux/fs.h
20 .. kernel-doc:: fs/dcache.c
23 .. kernel-doc:: include/linux/dcache.h
29 .. kernel-doc:: fs/inode.c
32 .. kernel-doc:: fs/bad_inode.c
38 .. kernel-doc:: fs/super.c
44 .. kernel-doc:: fs/locks.c
47 .. kernel-doc:: fs/locks.c
53 .. kernel-doc:: fs/mpage.c
56 .. kernel-doc:: fs/namei.c
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | README.rst | 3 Linux kernel release 6.x <http://kernel.org/>
8 kernel, and what to do if something goes wrong.
39 Linux has also been ported to itself. You can now run the kernel as a
53 these typically contain kernel-specific installation notes for some
57 your kernel.
59 Installing the kernel source
62 - If you install the full sources, put the kernel tarball in a
68 Replace "X" with the version number of the latest kernel.
71 incomplete) set of kernel headers that are used by the library header
73 whatever the kernel-du-jour happens to be.
[all …]
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| H A D | tracepoints.rst | 11 kernel tracepoints interfaces (refer to Documentation/trace/ftrace.rst).
13 For the list of support mlx5 events, check /sys/kernel/tracing/events/mlx5/.
19 $ echo mlx5:mlx5e_configure_flower >> /sys/kernel/tracing/set_event
20 $ cat /sys/kernel/tracing/trace
26 $ echo mlx5:mlx5e_delete_flower >> /sys/kernel/tracing/set_event
27 $ cat /sys/kernel/tracing/trace
33 $ echo mlx5:mlx5e_stats_flower >> /sys/kernel/tracing/set_event
34 $ cat /sys/kernel/tracing/trace
40 $ echo mlx5:mlx5e_tc_update_neigh_used_value >> /sys/kernel/tracing/set_event
41 $ cat /sys/kernel/tracing/trace
[all …]
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| 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 …]
|