Searched +full:built +full:- +full:in (Results 1 – 25 of 380) 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:
24 * Legalese - firmware is non-GPL compatible
28 * Some firmware files may be really large in size. The remote-proc subsystem
|
| /Documentation/dev-tools/kunit/ |
| D | run_manual.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 include KUnit in any kernel, read out results, and parse manually.
11 .. note:: KUnit is not designed for use in a production system. It is
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
[all …]
|
| D | faq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 test a single unit of code in isolation and hence the name *unit test*. A unit
15 code paths to be tested in the code under test. This is only possible if the
20 require installing the kernel on a test machine or in a virtual machine. All
21 testing frameworks require tests to be written in userspace and run on the
32 kernel and runs when the kernel boots, or when built as a module, when the
35 (see :ref:`kunit-on-qemu`).
37 In short, yes, you can run KUnit on other architectures, but it might require
40 For more information, see :ref:`kunit-on-non-uml`.
42 .. _kinds-of-tests:
[all …]
|
| /Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 6 -------
9 two languages in one. One language describes dependency graphs consisting of
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 ---------
[all …]
|
| D | kbuild.rst | 10 -------------
11 This file records the order in which modules appear in Makefiles. This
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 ---------
37 will be used in all cases where kbuild does preprocessing including
[all …]
|
| D | makefiles.rst | 16 kbuild Makefiles exist in every subdirectory
29 architecture-specific information to the top Makefile.
34 any built-in or modular targets.
51 working on. In order to do this effectively, they need some overall
69 kbuild infrastructure. This chapter introduces the syntax used in the
80 ----------------
83 These lines define the files to be built, any special compilation
90 obj-y += foo.o
92 This tells kbuild that there is one object in that directory, named
93 foo.o. foo.o will be built from foo.c or foo.S.
[all …]
|
| D | modules.rst | 5 This document describes how to build an out-of-tree kernel module.
11 kbuild to stay compatible with changes in the build infrastructure and
13 both in-tree and out-of-tree is provided. The method for building
14 either is similar, and all modules are initially developed and built
15 out-of-tree.
17 Covered in this document is information aimed at developers interested
18 in building out-of-tree (or "external") modules. The author of an
21 easily accomplished, and a complete example will be presented in
29 that contains the configuration and header files used in the build.
30 Also, the kernel must have been built with modules enabled. If you are
[all …]
|
| D | headers_install.rst | 5 The "make headers_install" command exports the kernel's header files in a
14 installed at the default location /usr/include and the kernel headers in
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
24 The "make headers_install" command can be run in the top level directory of the
25 kernel source code (or using a standard out-of-tree build). It takes two
32 is platform-specific, to see a complete list of supported architectures use
35 ls -d include/asm-* | sed 's/.*-//'
41 headers are installed in 'INSTALL_HDR_PATH/include'.
|
| /Documentation/admin-guide/nfs/ |
| D | nfs-rdma.rst | 17 The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server
18 was first included in the following release, Linux 2.6.25.
20 In our testing, we have obtained excellent performance results (full 10Gbit
29 nfs-rdma-devel@lists.sourceforge.net mailing list.
37 - Install an RDMA device
39 Any device supported by the drivers in drivers/infiniband/hw is acceptable.
41 Testing has been performed using several Mellanox-based IB cards, the
44 - Install a Linux distribution and tools
50 The procedures described in this document have been tested with
53 - Install nfs-utils-1.1.2 or greater on the client
[all …]
|
| /Documentation/sound/cards/ |
| D | joystick.rst | 10 -------
17 cards. In the case of ISA (PnP) cards, it's usually handled by the
19 built-in gameport support. Hence, when the ALSA PCI driver is built
20 in the kernel, CONFIG_GAMEPORT must be 'y', too. Otherwise, the
24 the load time. It'd be safer to plug in the joystick device before
29 ---------
33 joystick support is always enabled. In the former ALSA version, there
43 als4000 joystick_port 0 = disable (default), 1 = auto-detect,
46 azf3328 joystick 0 = disable, 1 = enable, -1 = auto (default)
48 ens1371 joystick_port 0 = disable (default), 1 = auto-detect,
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-module | 5 The name of the module that is in the kernel. This
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
12 by design and may be removed in the future.
24 placed in this location within sysfs. See the
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
59 version is returned in the following format::
62 Git: g[a-f0-9]\+(-dirty)\?
63 Mercurial: hg[a-f0-9]\+(-dirty)\?
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-toshiba_haps | 5 Description: This file controls the built-in accelerometer protection level,
8 * 0 -> Disabled
9 * 1 -> Low
10 * 2 -> Medium
11 * 3 -> High
20 Description: This file turns off the built-in accelerometer for a few
|
| D | debugfs-pfo-nx-crypto | 1 What: /sys/kernel/debug/nx-crypto/*
7 These debugfs interfaces are built by the nx-crypto driver, built in
18 The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not
19 recorded here (the hcall will retry until -EBUSY goes away).
29 The total number of bytes encrypted using AES in any of the driver's
36 The total number of bytes hashed by the hardware using SHA-256.
39 The total number of SHA-256 operations submitted to the hardware.
42 The total number of bytes hashed by the hardware using SHA-512.
45 The total number of SHA-512 operations submitted to the hardware.
|
| D | debugfs-scmi-raw | 7 in little-endian binary format to have it sent to the configured
11 Each write to the entry causes one command request to be built
22 in little-endian binary format to have it sent to the configured
29 Each write to the entry causes one command request to be built
38 Description: SCMI Raw message errors facility; any kind of timed-out or
65 different test-run.
74 in little-endian binary format to have it sent to the configured
80 Each write to the entry causes one command request to be built
84 has been associated with this transport channel in the DT
87 Note that these per-channel entries rooted at <..>/channels
[all …]
|
| /Documentation/scsi/ |
| D | scsi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 the SCSI subsystem in the Linux kernel (lk) 2.4 series. See:
9 https://www.tldp.org/HOWTO/SCSI-2.4-HOWTO . The LDP has single
12 Notes on using modules in the SCSI subsystem
14 The SCSI support in the Linux kernel can be modularized in a number of
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
23 unloaded. In practice the modprobe and rmmod commands
24 will enforce the correct ordering of loading and unloading modules in
27 The individual upper and lower level drivers can be loaded in any order
[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
18 maintainers interested in the Rust support, so that they can start working on
22 If you are an end user, please note that there are currently no in-tree
24 support is still in development/experimental, especially for certain kernel
29 ------------------
36 This kernel documentation was built with `Rust code documentation
41 This kernel documentation was not built with Rust code documentation.
[all …]
|
| D | testing.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 This document contains useful information how to test the Rust code in the
11 - The KUnit tests.
12 - The ``#[test]`` tests.
13 - The Kselftests.
16 ---------------
18 These are the tests that come from the examples in the Rust documentation. They
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
[all …]
|
| /Documentation/arch/x86/x86_64/ |
| D | uefi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The nomenclature EFI and UEFI are used interchangeably in this document.
21 ---------
23 - Build the kernel with the following configuration::
34 - Create a VFAT partition on the disk
35 - Copy the following to the VFAT partition:
38 kernel image built in first step and corresponding
40 can be found in the elilo sourceforge project.
42 - Boot to EFI shell and invoke elilo choosing the kernel image built
43 in first step.
[all …]
|
| /Documentation/virt/hyperv/ |
| D | overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 enlightened guest on Microsoft's Hyper-V hypervisor. Hyper-V
7 consists primarily of a bare-metal hypervisor plus a virtual machine
8 management service running in the parent partition (roughly
9 equivalent to KVM and QEMU, for example). Guest VMs run in child
10 partitions. In this documentation, references to Hyper-V usually
15 Hyper-V runs on x86/x64 and arm64 architectures, and Linux guests
16 are supported on both. The functionality and behavior of Hyper-V is
19 Linux Guest Communication with Hyper-V
20 --------------------------------------
[all …]
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | qca,ar9331.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Atheros AR9331 built-in switch
10 - Oleksij Rempel <o.rempel@pengutronix.de>
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.
18 const: qca,ar9331-switch
26 interrupt-controller: true
28 '#interrupt-cells':
[all …]
|
| /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
10 ``"security=..."`` kernel command line argument, in the case where multiple
11 LSMs were built into a given kernel.
15 include SELinux, Smack, Tomoyo, and AppArmor. In addition to the larger
16 MAC extensions, other extensions can be built using the LSM to provide
18 in the core functionality of Linux itself.
22 For more details on capabilities, see ``capabilities(7)`` in the Linux
23 man-pages project.
28 order in which checks are made. The capability module will always
[all …]
|
| /Documentation/admin-guide/ |
| D | verify-bugs-and-bisect-regressions.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
8 This document describes how to check if some Linux kernel problem occurs in code
9 currently supported by developers -- to then explain how to locate the change
22 read and navigate this document -- especially when you want to look something
23 up in the reference section, then jump back to where you left off.
26 https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
32 over to the* ':ref:`step-by-step guide <introguide_bissbs>`' *below. It utilizes
33 the same commands as this section while describing them in brief fashion. The
35 in a reference section mention many alternatives, pitfalls, and additional
36 aspects, all of which might be essential in your present case.]*
[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
35 a configuration file in /etc/modprobe.d/ instead::
|
| /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
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 -------------------
33 Your cpio archive should be specified in CONFIG_INITRAMFS_SOURCE and it
34 will be used directly. Only a single cpio file may be specified in
35 CONFIG_INITRAMFS_SOURCE and directory and file names are not allowed in
[all …]
|
| /Documentation/arch/powerpc/ |
| D | bootwrapper.rst | 10 be adaptable for each kind of image that needs to be built.
12 The boot wrapper can be found in the arch/powerpc/boot/ directory. The
13 Makefile in that directory has targets for all the available image types.
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
23 image. The details of the build system is discussed in the next section.
28 U-Boot (for versions that don't understand the device
31 are all embedded inside the U-Boot uImage file format
36 Because of the series of #ifdefs found in the
37 bd_info structure used in the old U-Boot interfaces,
[all …]
|
12345678910>>...16