Searched +full:built +full:- +full:into (Results 1 – 25 of 247) sorted by relevance
12345678910
| /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
6 into vmlinux directly, to enable avoiding having to look for firmware from
8 directly. You can enable built-in firmware using the kernel configuration
15 into the kernel with CONFIG_EXTRA_FIRMWARE:
19 want to stuff the firmware into the boot initramfs.
22 able to make use of built-in firmware:
24 * Legalese - firmware is non-GPL compatible
28 * Some firmware files may be really large in size. The remote-proc subsystem
|
| D | direct-fs-lookup.rst | 10 The max path allowed is PATH_MAX -- currently this is 4096 characters.
18 ----------------------
20 Drivers which are built-in to the kernel should have the firmware integrated
23 available. Stuffing the firmware into initramfs resolves this race issue,
26 There are circumstances that justify not wanting to include firmware into
28 remote-proc subsystem. For such cases using a userspace fallback mechanism
|
| /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
53 Description: This read-only file will appear if modpost was supplied with an
62 Git: g[a-f0-9]\+(-dirty)\?
63 Mercurial: hg[a-f0-9]\+(-dirty)\?
64 Subversion: svn[0-9]\+
|
| /Documentation/scsi/ |
| D | scsi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 https://www.tldp.org/HOWTO/SCSI-2.4-HOWTO . The LDP has single
18 The scsi-core (also known as the "mid level") contains the core of SCSI
20 The SCSI core support can be a module (scsi_mod.o), or it can be built into
29 as a module). The disk driver (sd_mod.o), CD-ROM driver (sr_mod.o),
40 Adaptec. Almost all lower level drivers can be built either as modules or
41 built into the kernel.
|
| /Documentation/kbuild/ |
| D | kbuild.rst | 10 -------------
16 ---------------
17 This file lists all modules that are built into the kernel. This is used
21 -----------------------
22 This file contains modinfo from all modules that are built into the kernel.
26 ----------------------
28 that are built into the kernel. Together with System.map, it can be used
35 ---------
41 ----------------
46 -------
[all …]
|
| D | makefiles.rst | 23 It builds these goals by recursively descending into the subdirectories of
29 architecture-specific information to the top Makefile.
34 any built-in or modular targets.
80 ----------------
83 These lines define the files to be built, any special compilation
90 obj-y += foo.o
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.
100 obj-$(CONFIG_FOO) += foo.o
102 $(CONFIG_FOO) evaluates to either y (for built-in) or m (for module).
[all …]
|
| D | kconfig-macro-language.rst | 6 -------
21 $(CC) -o $(APP) $(SRC)
27 gcc -o foo foo.c
32 The idea is quite similar in Kconfig - it is possible to describe a Kconfig
38 def_bool $(shell, $(srctree)/scripts/gcc-check-foo.sh $(CC))
40 The macro language in Kconfig processes the source file into the following
46 Then, Kconfig moves onto the evaluation stage to resolve inter-symbol
47 dependency as explained in kconfig-language.rst.
51 ---------
56 $( ). The parentheses are required even for single-letter variable names; $X is
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | run_manual.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 - We have an existing kernel configuration to test.
21 - Need to run on real hardware (or using an emulator/VM kunit_tool
23 - Wish to integrate with some existing testing systems.
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
[all …]
|
| D | architecture.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The KUnit architecture is divided into two parts:
9 - `In-Kernel Testing Framework`_
10 - `kunit_tool (Command-line Test Harness)`_
12 In-Kernel Testing Framework
19 - Organizes tests
20 - Reports test results
21 - Provides test utilities
24 ----------
27 into suites. A KUnit test case is a function with type signature
[all …]
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-xtensa-xtfpga.txt | 3 This simple SPI master controller is built into xtfpga bitstreams and is used
7 - compatible: should be "cdns,xtfpga-spi".
8 - reg: physical base address of the controller and length of memory mapped
|
| /Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 5 Last update: 2004-12-20 tlh
15 - gen_init_cpio, a program that builds a cpio-format archive
17 the compressed image is linked into the kernel image.
18 - initramfs, a chunk of code that unpacks the compressed cpio image
20 - klibc, a userspace C library, currently packaged separately, that is
23 The cpio file format used by initramfs is the "newc" (aka "cpio -H newc")
24 format, and is documented in the file "buffer-format.txt". There are
30 -------------------
39 ---------------------
43 a way to create images with root-owned files even though the image was
[all …]
|
| /Documentation/i2c/busses/ |
| D | scx200_acb.rst | 5 Author: Christer Weinigel <wingel@nano-system.com>
7 The driver supersedes the older, never merged driver named i2c-nscacb.
10 -----------------
20 -----------
25 Device-specific notes
26 ---------------------
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/trace/coresight/ |
| D | coresight-config.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 programming of the CoreSight system with pre-defined configurations that
17 Many CoreSight components can be programmed in complex ways - especially ETMs.
30 --------
37 a matching device, either when the feature is loaded into the system, or when the
40 The load process involves interpreting the descriptor into a set of register
41 accesses in the driver - the resource usage and parameter descriptions
42 translated into appropriate register accesses. This interpretation makes it easy
47 will be programmed into the device hardware.
67 system - which is described below.
[all …]
|
| /Documentation/rust/ |
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 in the kernel, please read the quick-start.rst guide.
11 -------------------
13 The Rust support was merged in v6.1 into mainline in order to help in
22 If you are an end user, please note that there are currently no in-tree
29 ------------------
36 This kernel documentation was built with `Rust code documentation
41 This kernel documentation was not built with Rust code documentation.
53 quick-start
54 general-information
[all …]
|
| D | testing.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 - The KUnit tests.
12 - The ``#[test]`` tests.
13 - The Kselftests.
16 ---------------
19 get transformed into KUnit tests.
27 ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --arch x86_64 --kconfig_add CONFIG_RUST=y
29 Alternatively, KUnit can run them as kernel built-in at boot. Refer to
30 Documentation/dev-tools/kunit/index.rst for the general KUnit documentation
31 and Documentation/dev-tools/kunit/architecture.rst for the details of kernel
[all …]
|
| D | general-information.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 ----------
13 The Rust support in the kernel can link only `core <https://doc.rust-lang.org/core/>`_,
14 but not `std <https://doc.rust-lang.org/std/>`_. Crates for use in the
15 kernel must opt into this behavior using the ``#![no_std]`` attribute.
21 ------------------
23 Rust kernel code is documented using ``rustdoc``, its built-in documentation
31 For linux-next, please see:
49 xdg-open Documentation/output/rust/rustdoc/kernel/index.html
51 To learn about how to write the documentation, please see coding-guidelines.rst.
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | cdns,xtfpga-i2s.txt | 1 Bindings for I2S controller built into xtfpga Xtensa bitstreams.
4 - compatible: shall be "cdns,xtfpga-i2s".
5 - reg: memory region (address and length) with device registers.
6 - interrupts: interrupt for the device.
7 - clocks: phandle to the clk used as master clock. I2S bus clock
12 i2s0: xtfpga-i2s@d080000 {
13 #sound-dai-cells = <0>;
14 compatible = "cdns,xtfpga-i2s";
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-grgpio.txt | 6 these properties are built from information in the AMBA plug&play.
10 - name : Should be "GAISLER_GPIO" or "01_01a"
12 - reg : Address and length of the register set for the device
14 - interrupts : Interrupt numbers for this device
18 - nbits : The number of gpio lines. If not present driver assumes 32 lines.
20 - irqmap : An array with an index for each gpio line. An index is either a valid
21 index into the interrupts property array, or 0xffffffff that indicates
|
| /Documentation/admin-guide/LSM/ |
| D | index.rst | 8 loadable kernel modules. Instead, they are selectable at build-time via
9 CONFIG_DEFAULT_SECURITY and can be overridden at boot-time via the
11 LSMs were built into a given kernel.
16 MAC extensions, other extensions can be built using the LSM to provide
23 man-pages project.
|
| /Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 5 The RapidIO standard is a packet-based fabric interconnect standard designed for
8 is publicly available for download from the RTA web-site [1].
17 into the kernel similarly to other buses by defining RapidIO-specific device and
21 architecture-specific interfaces that provide support for common RapidIO
33 ---------------
50 ----------
54 structure. Devices form one global device list and per-network device lists
58 ----------
68 specific switch drivers that are designed to provide hardware-specific
72 -----------
[all …]
|
| /Documentation/admin-guide/ |
| D | rtc.rst | 8 the local time zone or daylight savings time -- unless they dual boot
9 with MS-Windows -- but will instead be set to Coordinated Universal Time
12 The newest non-PC hardware tends to just count seconds, like the time(2)
16 Linux has two largely-compatible userspace RTC API families you may
20 so it's not very portable to non-x86 systems.
35 Old PC/AT-Compatible driver: /dev/rtc
36 --------------------------------------
38 All PCs (even Alpha machines) have a Real Time Clock built into them.
39 Usually they are built into the chipset of the computer, but some may
44 a few ways (enabling longer alarm periods, and wake-from-hibernate).
[all …]
|
| D | module-signing.rst | 2 ------------------------------
6 .. - Overview.
7 .. - Configuring module signing.
8 .. - Generating signing keys.
9 .. - Public keys in the kernel.
10 .. - Manually signing modules.
11 .. - Signed modules and stripping.
12 .. - Loading signed modules.
13 .. - Non-valid signatures and unsigned modules.
14 .. - Administering/protecting the private key.
[all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | aspeed,ast2600-adc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/iio/adc/aspeed,ast2600-adc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Billy Tsai <billy_tsai@aspeedtech.com>
13 • 10-bits resolution for 16 voltage channels.
14 • The device split into two individual engine and each contains 8 voltage
16 • Channel scanning can be non-continuous.
21 • Built-in a compensating method.
22 • Built-in a register to trim internal reference voltage.
[all …]
|
| /Documentation/arch/powerpc/ |
| D | bootwrapper.rst | 10 be adaptable for each kind of image that needs to be built.
17 others. U-Boot is typically found on embedded PowerPC hardware, but there
21 The boot wrapper is built from the makefile in arch/powerpc/boot/Makefile and
28 U-Boot (for versions that don't understand the device
31 are all embedded inside the U-Boot uImage file format
33 bd_info structure and loads the data into the device
34 tree before jumping into the kernel.
37 bd_info structure used in the old U-Boot interfaces,
39 U-Boot platform has a different platform init file
77 uImage: Native image format used by U-Boot. The uImage target
[all …]
|
| /Documentation/core-api/ |
| D | printk-index.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 Finding these changes in the sources would require non-trivial parsers.
35 The index of printk formats are split in into separate files. The files are
36 named according to the binaries where the printk formats are built-in. There
44 might appear in "vmlinux" when the module is built-in.
48 $> head -1 /sys/kernel/debug/printk/index/vmlinux; shuf -n 5 vmlinux
50 <5> block/blk-settings.c:661 disk_stack_limits "%s: Warning: Device %s is misaligned\n"
54 <6> drivers/acpi/osl.c:1410 acpi_no_auto_serialize_setup "ACPI: auto-serialization disabled\n"
58 - :level: log level value: 0-7 for particular severity, -1 as default,
60 - :flags: optional flags: currently only 'c' for KERN_CONT
[all …]
|
12345678910