| /kernel/linux/linux-5.10/tools/build/Documentation/ |
| D | Build.txt | 1 Build Framework
4 The perf build framework was adopted from the kernel build system, hence the
7 Basically the user provides set of 'Build' files that list objects and
8 directories to nest for specific target to be build.
10 Unlike the kernel we don't have a single build object 'obj-y' list that where
11 we setup source objects, but we support more. This allows one 'Build' file to
12 carry a sources list for multiple build objects.
15 Build framework makefiles
18 The build framework consists of 2 Makefiles:
20 Build.include
[all …]
|
| /kernel/linux/linux-5.10/samples/ |
| D | Kconfig | 5 You can build and test sample kernel code here.
14 tristate "Build trace_events examples -- loadable modules only"
17 This build trace event example modules.
20 tristate "Build trace_printk module - tests various trace_printk formats"
27 tristate "Build register_ftrace_direct() example"
35 tristate "Build sample module for kernel access to Ftrace instancess"
42 tristate "Build kobject examples"
44 This config option will allow you to build a number of
51 tristate "Build kprobes examples -- loadable modules only"
54 This build several kprobes example modules.
[all …]
|
| /kernel/linux/linux-5.10/drivers/block/paride/ |
| D | Kconfig | 17 connected through a parallel port. If you chose to build PARIDE
18 support into your kernel, you may answer Y here to build in the
19 parallel port IDE driver, otherwise you should answer M to build
33 connected through a parallel port. If you chose to build PARIDE
34 support into your kernel, you may answer Y here to build in the
36 build it as a loadable module. The module will be called pcd. You
49 connected through a parallel port. If you chose to build PARIDE
50 support into your kernel, you may answer Y here to build in the
52 to build it as a loadable module. The module will be called pf.
63 connected through a parallel port. If you chose to build PARIDE
[all …]
|
| /kernel/linux/linux-5.10/tools/build/feature/ |
| D | Makefile | 84 BUILD = $(__BUILD) > $(@:.bin=.make.output) 2>&1 macro
92 …$(BUILD) -fstack-protector-all -O2 -D_FORTIFY_SOURCE=2 -ldw -lelf -lnuma -lelf -I/usr/include/slan…
95 $(BUILD)
98 $(BUILD) -D_GNU_SOURCE -lpthread
101 $(BUILD) -lpthread
104 $(BUILD) -fstack-protector-all
107 $(BUILD) -O2 -D_FORTIFY_SOURCE=2
110 $(BUILD)
113 $(BUILD) -lcap
116 $(BUILD) -lelf
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | Build.txt | 2 1) perf build
4 The perf build process consists of several separated building blocks,
11 Several makefiles govern the perf build:
18 main makefile that triggers build of all perf objects including
21 - tools/build/Makefile.build
22 main makefile of the build framework
24 - tools/build/Build.include
25 build framework generic definitions
27 - Build makefiles
28 makefiles that defines build objects
[all …]
|
| /kernel/linux/linux-5.10/drivers/accessibility/speakup/ |
| D | Kconfig | 54 synthesizer. You can say y to build it into the kernel,
55 or m to build it as a module. See the configuration
63 synthesizer. You can say y to build it into the kernel,
64 or m to build it as a module. See the configuration
71 synthesizer. You can say y to build it into the kernel,
72 or m to build it as a module. See the configuration
79 You can say y to build it into the kernel, or m to
80 build it as a module. See the configuration help on the
87 synthesizer. You can say y to build it into the kernel,
88 or m to build it as a module. See the configuration
[all …]
|
| /kernel/linux/patches/ |
| D | README.md | 6 - [Build](#section19369206113115)
17 During the build process, you can merge the driver code based on the chip platform and build the ke…
23 ├── build
24 │ ├── BUILD.gn # GN file of the build framework
25 │ ├── kernel.mk # Kernel build file
26 │ └── ohos.build # Kernel build component file
64 …nel version. For details, see the method in **kernel.mk** in the **kernel/linux/build** repository.
74 …es for the patches of the chip component in **kernel.mk** in the **kernel/linux/build** repository.
81 3. Modify the **config** file to build.
83 …h and naming rules of the chip component in **kernel.mk** in the **kernel/linux/build** repository.
[all …]
|
| /kernel/linux/linux-5.10/drivers/clk/rockchip/ |
| D | Kconfig | 16 Build the driver for PX30 Clock Driver.
22 Build the driver for RV110x Clock Driver.
28 Build the driver for RK3036 Clock Driver.
34 Build the driver for RK312x Clock Driver.
40 Build the driver for RK3188 Clock Driver.
46 Build the driver for RK322x Clock Driver.
53 Build the driver for RK3288 Clock Driver.
59 Build the driver for RK3308 Clock Driver.
65 Build the driver for RK3328 Clock Driver.
71 Build the driver for RK3368 Clock Driver.
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/accel/ |
| D | Kconfig | 15 Say Y here to build support for Analog Devices adis16201 dual-axis
27 Say Y here to build support for Analog Devices adis16209 dual-axis digital inclinometer
43 Say Y here if you want to build support for the Analog Devices
57 Say Y here if you want to build support for the Analog Devices
97 Say Y here if you want to build a driver for the Bosch BMA023, BMA150
121 Say Y here if you want to build a driver for the Bosch BMA400
145 Say yes here to build support for the following Bosch accelerometers:
164 Say yes here to build support for the MiraMEMS DA280 3-axis 14-bit
174 Say yes here to build support for the MiraMEMS DA311 3-axis 12-bit
185 Say yes here to build support for the Domintech low-g tri-axial
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/adc/ |
| D | Kconfig | 29 Say yes here to build support for Analog Devices AD7091R-5 ADC.
36 Say yes here to build support for Analog Devices AD7124-4 and AD7124-8
47 Say yes here to build support for Analog Devices AD7190,
61 Say yes here to build support for Analog Devices AD7265 and AD7266
71 Say yes here to build support for Analog Devices AD7291
81 Say yes here to build support for Analog Devices AD7292
93 Say yes here to build support for Analog Devices AD7298
105 Say yes here to build support for the following SPI analog to
125 Say yes here to build parallel interface support for Analog Devices:
136 Say yes here to build spi interface support for Analog Devices:
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/dac/ |
| D | Kconfig | 13 Say yes here to build support for Analog Devices AD5024, AD5025, AD5044,
27 Say yes here to build support for Analog Devices AD5360, AD5361,
40 Say yes here to build support for Analog Devices AD5380, AD5381,
51 Say yes here to build support for Analog Devices AD5421 loop-powered
61 Say yes here to build support for Analog Devices AD5300, AD5301, AD5310,
74 Say yes here to build support for Analog Devices AD5415, AD5426, AD5429,
89 Say yes here to build support for Analog Devices AD5592R
101 Say yes here to build support for Analog Devices AD5593R
111 Say yes here to build support for Analog Devices AD5504, AD5501,
121 Say yes here to build support for Analog Devices AD5624R, AD5644R and
[all …]
|
| /kernel/linux/build/ |
| D | README.md | 7 - [Build](#section19369206113115)
18 During the build process, you can merge the driver code based on the chip platform and build the ke…
49 …nel version. For details, see the method in **kernel.mk** in the **kernel/linux/build** repository.
59 …es for the patches of the chip component in **kernel.mk** in the **kernel/linux/build** repository.
66 3. Modify the **config** file to build.
68 …h and naming rules of the chip component in **kernel.mk** in the **kernel/linux/build** repository.
77 …Harmony project build process, patches are installed after **kernel/linux/linux-\*\.\*** is copied…
82 ## Build<a name="section19369206113115"></a>
86 Perform a full build for the project to generate the **uImage** kernel image.
89 ./build.sh --product-name Hi3516DV300 # Build the Hi3516D V300 image.
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/light/ |
| D | Kconfig | 17 Say Y here if you want to build a driver for the ACPI0008
40 Say Y here if you want to build a driver for the Analog Devices
50 Say Y here if you want to build a driver for the Dyna Image AL3010
60 Say Y here if you want to build a driver for the Dyna Image AL3320A
70 Say Y here if you want to build a driver for the Avago APDS9300
83 Say Y here to build I2C interface support for the Avago
108 Say Y here to build support for the ROHM BH1710, BH1715, BH1721,
118 Say Y here to build support for the ROHM BH1780GLI ambient
150 Say Y here if you want to build a driver for Capella CM3323
160 Say Y here if you want to build a driver for Capella CM3605
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/pressure/ |
| D | Kconfig | 13 Say yes here to build support for the Honeywell ABP pressure
26 Say yes here to build support for Bosch Sensortec BMP180 and BMP280
50 Say yes here to build support for the Barometer sensor when
62 Say yes here to build support for the All Sensors DLH series
86 Say yes here to build support for the HID SENSOR
97 Say yes here to build support for Hope RF HP03 pressure and
108 Say yes here to build support for InvenSense ICP-101xx barometric
122 Say yes here to build support for the Freescale MPL115A2
133 Say yes here to build support for the Freescale MPL115A1
145 Say yes here to build support for the Freescale MPL3115A2
[all …]
|
| /kernel/linux/linux-5.10/drivers/clk/hisilicon/ |
| D | Kconfig | 8 Build the clock driver for hi3516cv300.
16 Build the clock driver for hi3519.
23 Build the clock driver for hi3660.
30 Build the clock driver for hi3670.
38 Build the clock driver for hi3798cv200.
45 Build the Hisilicon Hi6220 clock driver based on the common clock framework.
52 Build reset controller driver for HiSilicon device chipsets.
60 Build the Hisilicon Hi6220 stub clock driver.
68 Build the Hisilicon Hi3660 stub clock driver.
|
| /kernel/linux/linux-5.10/drivers/iio/chemical/ |
| D | Kconfig | 16 Say Y here to build I2C interface support for the following
29 Say Y here to build I2C interface support for the following
43 Say yes here to build support for Bosch Sensortec BME680 sensor with
65 Say Y here to build I2C interface support for the AMS
72 Say Y here to build I2C interface support for the AMS
82 Say Y here to build support for the Plantower PMS7003 particulate
93 Say Y here to build support for the Sensirion SCD30 sensor with carbon
104 Say Y here to build support for the Sensirion SCD30 I2C interface
115 Say Y here to build support for the Sensirion SCD30 serial interface
126 Say Y here to build I2C interface support for the following
[all …]
|
| /kernel/linux/linux-5.10/tools/build/ |
| D | Makefile.build | 3 # Main build makefile.
27 build-dir := $(srctree)/tools/build
31 fixdep := $(build-dir)/fixdep
37 include $(build-dir)/Build.include
42 # Init all relevant variables used in build files so
50 # Build definitions
51 build-file := $(dir)/Build
52 -include $(build-file)
94 # Build rules
119 # Gather build data:
[all …]
|
| /kernel/linux/config/ |
| D | README.md | 7 - [Build](#section19369206113115)
58 …nel version. For details, see the method in **kernel.mk** in the **kernel/linux/build** repository.
68 …es for the patches of the chip component in **kernel.mk** in the **kernel/linux/build** repository.
75 3. Modify the **config** file to build.
77 …h and naming rules of the chip component in **kernel.mk** in the **kernel/linux/build** repository.
86 …Harmony project build process, patches are installed after **kernel/linux/linux-\*\.\*** is copied…
90 ## Build<a name="section19369206113115"></a>
93 Perform a full build for the project to generate the **uImage** kernel image.
96 ./build.sh --product-name Hi3516DV300 # Build the Hi3516D V300 image.
97 --build-target build_kernel # Build the uImage kernel image of Hi3516D V300.
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/proximity/ |
| D | Kconfig | 14 Say Y here to build SPI interface support for the Austrian
31 Say Y here if you want to build a driver for the Intersil ISL29501
43 Say Y to build a driver for PulsedLight LIDAR range finding
53 Say Y to build a driver for the ultrasonic sensors I2CXL of
65 Say Y here to build a driver for GPIO bitbanged ranger sensors
80 Say Y to build a driver for the RFD77402 Time-of-Flight (distance)
90 Say Y here to build a driver for GPIO bitbanged ultrasonic
111 Say Y here to build a driver for Semtech's SX9310/SX9311 capacitive
124 Say Y here to build a driver for Semtech's SX9500 capacitive
136 Say Y here to build a driver for Devantech SRF02/SRF08/SRF10
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/ |
| D | Makefile | 92 # implicit rules to sub-test Makefiles which avoids build failures in test
93 # Makefile that don't have explicit build rules.
120 BUILD := $(abs_objtree)/kselftest macro
122 BUILD := $(CURDIR) macro
130 export BUILD
132 # build and run gpio when output directory is the src dir.
158 # Local build cases: "make kselftest", "make -C" - headers are installed
164 $(MAKE) --no-builtin-rules INSTALL_HDR_PATH=$$BUILD/usr \
171 BUILD_TARGET=$$BUILD/$$TARGET; \
180 BUILD_TARGET=$$BUILD/$$TARGET; \
[all …]
|
| /kernel/linux/linux-5.10/samples/bpf/ |
| D | README.rst | 7 Build dependencies
40 This will creates a local "usr/include" directory in the git/build top
60 By default llvm will build all non-experimental backends including bpf.
66 (build dependencies are cmake and gcc-c++)::
71 $ cd ..; mkdir build; cd build
78 make M=samples/bpf LLC=~/git/llvm/build/bin/llc CLANG=~/git/llvm/build/bin/clang
85 build samples for the cross target::
97 Build samples::
101 Or build samples with SYSROOT if some header or library is absent in toolchain,
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/ |
| D | gdb-kernel-debugging.rst | 30 - Build the kernel with CONFIG_GDB_SCRIPTS enabled, but leave
39 this mode. In this case, you should build the kernel with
51 - cd /path/to/linux-build
58 add-auto-load-safe-path /path/to/linux-build
74 scanning for modules in /home/user/linux/build
75 loading @0xffffffffa0020000: /home/user/linux/build/net/netfilter/xt_tcpudp.ko
76 loading @0xffffffffa0016000: /home/user/linux/build/net/netfilter/xt_pkttype.ko
77 loading @0xffffffffa0002000: /home/user/linux/build/net/netfilter/xt_limit.ko
78 loading @0xffffffffa00ca000: /home/user/linux/build/net/packet/af_packet.ko
79 loading @0xffffffffa003c000: /home/user/linux/build/fs/fuse/fuse.ko
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/potentiometer/ |
| D | Kconfig | 13 Say yes here to build support for the Analog Devices AD5272 and AD5274
23 Say yes here to build support for the Maxim Integrated DS1803
33 Say yes here to build support for the Maxim
44 Say yes here to build support for the Maxim
55 Say yes here to build support for the Maxim
66 Say yes here to build support for the Microchip
77 Say yes here to build support for the Microchip
95 Say yes here to build support for the Microchip
109 Say yes here to build support for the Microchip
122 Say yes here to build support for the Texas Instruments
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | reproducible-builds.rst | 7 exactly the same. This makes it possible to verify that the build
57 to an absolute filename in an out-of-tree build. Kbuild automatically
67 The build processes for some programs under the ``tools/``
69 cause a later source package build using e.g. ``make rpm-pkg`` to
78 generate a different temporary key for each build, resulting in the
82 One approach to this is to divide up the build process so that the
91 Build the kernel and modules.
96 4. Perform a second build that attaches the module signatures. It
113 Once you set all the necessary variables for a reproducible build, a
122 .. _KBUILD_BUILD_TIMESTAMP: kbuild.html#kbuild-build-timestamp
[all …]
|
| D | modules.rst | 5 This document describes how to build an out-of-tree kernel module.
10 === 2 How to Build External Modules
39 "kbuild" is the build system used by the Linux kernel. Modules must use
40 kbuild to stay compatible with changes in the build infrastructure and
49 complexity, so one only has to type "make" to build the module. This is
54 2. How to Build External Modules
57 To build external modules, you must have a prebuilt kernel available
58 that contains the configuration and header files used in the build.
68 NOTE: "modules_prepare" will not build Module.symvers even if
69 CONFIG_MODVERSIONS is set; therefore, a full kernel build needs to be
[all …]
|