| /linux/drivers/clk/ingenic/ |
| H A D | Kconfig | 16 If building for a JZ4740 SoC, you want to say Y here.
26 If building for a JZ4755 SoC, you want to say Y here.
36 If building for a JZ4725B SoC, you want to say Y here.
46 If building for a JZ4760 SoC, you want to say Y here.
56 If building for a JZ4770 SoC, you want to say Y here.
66 If building for a JZ4780 SoC, you want to say Y here.
76 If building for a X1000 SoC, you want to say Y here.
86 If building for a X1830 SoC, you want to say Y here.
|
| /linux/tools/tracing/rtla/ |
| H A D | Makefile.config | 60 $(info libcpupower is missing, building without --deepest-idle-state support.)
68 $(info libcheck is missing, building without unit tests support.)
79 $(info BPF skeleton support disabled, building without BPF skeleton support.)
86 $(info libbpf is missing, building without BPF skeleton support.)
95 $(info clang is missing or does not support BPF CO-RE, building without BPF skeleton support.)
104 $(info bpftool is missing or not supporting skeletons, building without BPF skeleton support.)
|
| /linux/drivers/usb/cdns3/ |
| H A D | Kconfig | 85 Say 'Y' or 'M' here if you are building for Texas Instruments
95 Say 'Y' or 'M' here if you are building for NXP i.MX
105 Say 'Y' or 'M' here if you are building for StarFive SoCs
|
| /linux/tools/perf/Documentation/ |
| H A D | Build.txt | 4 The perf build process consists of several separated building blocks,
82 Below is the command for building the perf with dynamic linking.
93 configuration paths for cross building:
|
| /linux/Documentation/arch/openrisc/ |
| H A D | openrisc_port.rst | 27 Instructions for building the different toolchains can be found on openrisc.io
33 building https://github.com/stffrdhrn/or1k-toolchain-build
36 2) Building
51 The OpenRISC community typically uses FuseSoC to manage building and programming
|
| /linux/include/linux/ |
| H A D | hidden.h | 3 * When building position independent code with GCC using the -fPIC option,
5 * building a dynamic object (either a shared library or an executable) that
|
| H A D | of_pdt.h | 3 * Definitions for building a device tree by calling into the
35 /* for building the device tree */
|
| /linux/Documentation/gpu/xe/ |
| H A D | xe_mm.rst | 25 Pagetable building
29 :doc: Pagetable building
|
| /linux/tools/perf/trace/beauty/ |
| H A D | sockaddr.sh | 7 # normal compiler building process and would drag needless stuff from the
12 # string table building scripts.
|
| /linux/Documentation/driver-api/firmware/ |
| H A D | built-in-fw.rst | 5 Firmware can be built-in to the kernel, this means building the firmware
14 There are a few reasons why you might want to consider building your firmware
|
| /linux/drivers/pinctrl/nuvoton/ |
| H A D | Kconfig | 17 building a kernel that will run on this chip.
47 building a kernel that will run on this chip.
|
| /linux/drivers/eisa/ |
| H A D | Kconfig | 21 Say Y here if you are building a kernel for an EISA-based machine.
70 you are building an installation floppy or kernel for an
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| H A D | media-controller-model.rst | 14 - An **entity** is a basic media hardware or software building block.
17 hardware devices (a building block in a System-on-Chip image
|
| /linux/tools/perf/tests/ |
| H A D | tests-scripts.c | 203 pr_err("Out of memory while building script test suite list\n"); in append_script()
216 pr_err("Out of memory while building script test suite list\n"); in append_script()
227 pr_err("Out of memory while building script test suite list\n"); in append_scripts_in_dir()
297 pr_err("Out of memory while building script test suite list\n");
|
| /linux/Documentation/networking/ |
| H A D | xdp-rx-metadata.rst | 86 conversion, and the XDP metadata is not used by the kernel when building
91 can override some of the metadata used for building ``skbs``.
151 does not exceed 252 bytes, and leaves sufficient space for building the
|
| /linux/drivers/platform/mellanox/ |
| H A D | Kconfig | 38 Centers (EDC) for building Ethernet based clusters, High-Performance
72 Centers (EDC) for building Ethernet based clusters, High-Performance
|
| /linux/samples/hid/ |
| H A D | Makefile.target | 3 # Building binaries on the host system
38 # Handle options to gcc. Support building with separate output directory
|
| /linux/samples/bpf/ |
| H A D | Makefile.target | 3 # Building binaries on the host system
38 # Handle options to gcc. Support building with separate output directory
|
| /linux/fs/jffs2/ |
| H A D | xattr.h | 56 uint32_t ino; /* only used in scanning/building */
60 uint32_t xid; /* only used in sccanning/building */
|
| /linux/Documentation/arch/arc/ |
| H A D | arc.rst | 52 Building the Linux kernel for ARC processors
55 The process of kernel building for ARC processors is the same as for any other
|
| /linux/Documentation/kbuild/ |
| H A D | gcc-plugins.rst | 14 The GCC plugin infrastructure of the kernel supports building out-of-tree
15 modules, cross-compilation and building in a separate directory.
|
| /linux/lib/zlib_inflate/ |
| H A D | inflate.h | 103 /* dynamic table building */
110 unsigned short work[288]; /* work area for code table building */
|
| /linux/Documentation/dev-tools/ |
| H A D | propeller.rst | 38 #. Initial building: Build the AutoFDO or AutoFDO+ThinLTO binary as
102 Here is an example workflow for building an AutoFDO+Propeller kernel:
|
| /linux/security/integrity/evm/ |
| H A D | Makefile | 3 # Makefile for building the Extended Verification Module(EVM)
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | start.rst | 47 Building KUnit Kernel ...
53 Because it is building a lot of sources for the first time,
54 the ``Building KUnit Kernel`` step may take a while.
|