Searched full:built (Results 1 – 25 of 392) sorted by relevance
12345678910>>...16
| /Documentation/driver-api/firmware/ |
| D | built-in-fw.rst | 2 Built-in firmware
5 Firmware can be built-in to the kernel, this means building the firmware
8 directly. You can enable built-in firmware using the kernel configuration
22 able to make use of built-in firmware:
|
| /Documentation/dev-tools/kunit/ |
| D | run_manual.rst | 26 tests can also be built by enabling their config options in our
28 ending in ``_KUNIT_TEST``. Most tests can either be built as a module,
29 or be built into the kernel.
38 Once we have built our kernel (and/or modules), it is simple to run
39 the tests. If the tests are built-in, they will run automatically on the
43 If the tests are built as modules, they will run when the module is
78 You can use the debugfs filesystem to trigger built-in tests to run after
|
| D | faq.rst | 32 kernel and runs when the kernel boots, or when built as a module, when the
84 filesystem mounted), and has had issues in the past when built statically and
96 built into any kernel, or can be built as a module and loaded at runtime.
98 seeing. When tests are built-in, they will execute when the kernel boots, and
|
| /Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 81 "user-defined function" in contrast to "built-in function" listed below).
93 Built-in functions
96 Like Make, Kconfig provides several built-in functions. Every function takes a
99 In Make, every built-in function takes at least one argument. Kconfig allows
100 zero argument for built-in functions, such as $(filename), $(lineno). You could
101 consider those as "built-in variable", but it is just a matter of how we call
102 it after all. Let's say "built-in function" here to refer to natively supported
105 Kconfig currently supports the following built-in functions.
172 In Make, a user-defined function is referenced by using a built-in function,
177 Kconfig invokes user-defined functions and built-in functions in the same way.
|
| D | kbuild.rst | 17 This file lists all modules that are built into the kernel. This is used
22 This file contains modinfo from all modules that are built into the kernel.
28 that are built into the kernel. Together with System.map, it can be used
47 Additional options to the assembler (for built-in and modules).
55 Additional assembler options for built-in.
59 Additional options to the C compiler (for built-in and modules).
63 Additional options to the Rust compiler (for built-in and modules).
68 code that is compiled as built-in.
77 code that is compiled as built-in.
154 building external modules against a pre-built kernel in a separate build
[all …]
|
| D | makefiles.rst | 34 any built-in or modular targets.
83 These lines define the files to be built, any special compilation
93 foo.o. foo.o will be built from foo.c or foo.S.
95 If foo.o shall be built as a module, the variable obj-m is used.
102 $(CONFIG_FOO) evaluates to either y (for built-in) or m (for module).
106 Built-in object goals - obj-y
114 ``$(AR) rcSTP`` to merge these files into one built-in.a file.
120 built-in.a and succeeding instances will be ignored.
139 $(obj-m) specifies object files which are built as loadable
142 A module may be built from one source file or several source
[all …]
|
| D | modules.rst | 14 either is similar, and all modules are initially developed and built
30 Also, the kernel must have been built with modules enabled. If you are
50 The kbuild system knows that an external module is being built
57 Then to install the module(s) just built, add the target
66 of the kernel output directory if the kernel was built in a separate
78 Informs kbuild that an external module is being built.
138 running kernel. The module is not actually built, however, because a
140 the module(s) being built, along with the list of requisite source
148 When the module is built from multiple sources, an additional line is
157 module 8123.ko, which is built from the following files::
|
| D | headers_install.rst | 19 means that a program built against a C library using older kernel headers
21 features), but a program built against newer kernel headers may not work on an
|
| /Documentation/admin-guide/nfs/ |
| D | nfs-rdma.rst | 139 and server will not be built
142 in this case the NFS/RDMA client and server will be built as modules
145 and server will be built into the kernel
148 the NFS/RDMA client and server will be built.
163 If you built the RDMA components as modules, load them at
247 If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
254 Regardless of how the server was built (module or built-in), start the
275 If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
282 Regardless of how the client was built (module or built-in), use this
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-toshiba_haps | 5 Description: This file controls the built-in accelerometer protection level,
20 Description: This file turns off the built-in accelerometer for a few
|
| D | debugfs-pfo-nx-crypto | 7 These debugfs interfaces are built by the nx-crypto driver, built in
|
| D | debugfs-scmi-raw | 11 Each write to the entry causes one command request to be built
29 Each write to the entry causes one command request to be built
80 Each write to the entry causes one command request to be built
107 Each write to the entry causes one command request to be built
|
| D | sysfs-platform-dell-privacy-wmi | 19 shutter assembly that is built onto the camera module to block capturing images
54 shutter assembly that is built onto the camera module to block capturing images
|
| /Documentation/sound/cards/ |
| D | joystick.rst | 19 built-in gameport support. Hence, when the ALSA PCI driver is built
79 built-in gameport support.
81 As mentioned above, ALSA PCI drivers have the built-in gameport
89 ALSA ISA drivers don't have the built-in gameport support.
|
| /Documentation/ABI/stable/ |
| D | sysfs-module | 7 dynamic module. If it is built directly into the kernel, it
11 Note: The conditions of creation in the built-in case are not
33 Note: If the module is built into the kernel, or if the
|
| /Documentation/scsi/ |
| D | scsi.rst | 20 The SCSI core support can be a module (scsi_mod.o), or it can be built into
40 Adaptec. Almost all lower level drivers can be built either as modules or
41 built into the kernel.
|
| /Documentation/i2c/busses/ |
| D | scx200_acb.rst | 29 If the scx200_acb driver is built into the kernel, add the following
34 If the scx200_acb driver is built as a module, add the following line to
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | qca,ar9331.yaml | 7 title: Qualcomm Atheros AR9331 built-in switch
13 Qualcomm Atheros AR9331 is a switch built-in to Atheros AR9331 WiSoC and
14 addressable over internal MDIO bus. All PHYs are built-in as well.
|
| /Documentation/rust/ |
| D | index.rst | 36 This kernel documentation was built with `Rust code documentation
41 This kernel documentation was not built with Rust code documentation.
|
| D | testing.rst | 29 Alternatively, KUnit can run them as kernel built-in at boot. Refer to
32 built-in vs. command line testing.
70 run against a built kernel.
148 The kselftests are built within the kernel source tree and are intended to
|
| /Documentation/arch/x86/x86_64/ |
| D | uefi.rst | 38 kernel image built in first step and corresponding
42 - Boot to EFI shell and invoke elilo choosing the kernel image built
|
| /Documentation/virt/hyperv/ |
| D | overview.rst | 43 * VMBus: VMBus is a higher-level software construct that is built on
200 The code in #1 and #2 is built only when CONFIG_HYPERV is set.
201 Similarly, the code for most Hyper-V related drivers is built only
204 Most Hyper-V related code in #1 and #3 can be built as a module.
205 The architecture specific code in #2 must be built-in. Also,
207 architectures and must be built-in.
|
| /Documentation/admin-guide/LSM/ |
| D | index.rst | 11 LSMs were built into a given kernel.
16 MAC extensions, other extensions can be built using the LSM to provide
|
| /Documentation/admin-guide/ |
| D | verify-bugs-and-bisect-regressions.rst | 104 # * Check how much space your self-built kernel actually needs, which
110 make -s kernelrelease | tee -a ~/kernels-built
112 # * Once booted, ensure you are running the kernel you just built by
114 tail -n 1 ~/kernels-built
156 works with the newly built kernel. If it does, tell Git by executing
188 remove some kernels you built earlier. You most likely want to keep those
189 you built during segment 1 and 2 around for a while, but you will most
204 free to remove all kernels built during the actual bisection (Segment 3 c);
205 the kernels you built earlier and later you might want to keep around for
466 something to keep in mind: if something is misbehaving with the kernels built
[all …]
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-xtensa-xtfpga.txt | 3 This simple SPI master controller is built into xtfpga bitstreams and is used
|
12345678910>>...16