| /openbmc/linux/drivers/base/firmware_loader/builtin/ |
| H A D | main.c | 1 // SPDX-License-Identifier: GPL-2.0
24 if (size < fw->size) in fw_copy_to_prealloc_buf()
26 memcpy(buf, fw->data, fw->size); in fw_copy_to_prealloc_buf()
31 * firmware_request_builtin() - load builtin firmware
38 * if the firmware was built-in and if so use it right away. This can be used
41 * This looks for the firmware in the built-in kernel. Only if the kernel was
42 * built-in with the firmware you are looking for will this return successfully.
55 if (strcmp(name, b_fw->name) == 0) { in firmware_request_builtin()
56 fw->size = b_fw->size; in firmware_request_builtin()
57 fw->data = b_fw->data; in firmware_request_builtin()
[all …]
|
| /openbmc/linux/drivers/accessibility/speakup/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
9 video console for blind people. If built in to the
12 point your browser at <http://www.linux-speakup.org/>.
24 Speakup can either be built in or compiled as a module
28 the synthesizer drivers below can only be built as
36 The Dectalk pc driver can only be built as a module, and
37 requires software to be pre-loaded on to the card before
55 synthesizer. You can say y to build it into the kernel,
64 synthesizer. You can say y to build it into the kernel,
72 synthesizer. You can say y to build it into the kernel,
[all …]
|
| /openbmc/linux/Documentation/driver-api/firmware/ |
| H A 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
|
| /openbmc/linux/drivers/base/firmware_loader/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
11 will first look for built-in firmware, if it has any. Next, it will
24 You typically want this built-in (=y) but you can also enable this
25 as a module, in which case the firmware_class module will be built.
26 You also want to be sure to enable this built-in if you are going to
27 enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
49 string "Build named firmware blobs into the kernel binary"
53 /lib/firmware/ paths. This option enables you to build into the
54 kernel firmware files. Built-in firmware searches are preceded
62 This option is a string and takes the (space-separated) names of the
[all …]
|
| /openbmc/linux/kernel/rcu/ |
| H A D | Kconfig.debug | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # RCU-related debugging configuration options
19 false-positive splats, we keep it default disabled but once all
33 tests on the RCU infrastructure. The kernel module may be built
36 Say Y here if you want RCU performance tests to be built into
48 on the RCU infrastructure. The kernel module may be built
51 Say Y here if you want RCU torture tests to be built into
57 tristate "Scalability tests for read-side synchronization (RCU and others)"
63 useful comparing RCU with various read-side synchronization mechanisms.
64 The kernel module may be built after the fact on the running kernel to be
[all …]
|
| /openbmc/linux/Documentation/kbuild/ |
| H A 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 …]
|
| H A 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.
30 ---------
36 -------
37 Additional options to the assembler (for built-in and modules).
40 -------------
44 -------------
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | prebuilt-libraries.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
3 Working with Pre-Built Libraries
10 release pre-built binaries. When shared libraries are built, they should
12 <https://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html>`__
20 running ``readelf -d filename | grep SONAME``.
23 pre-built libraries.
28 In this example we work with pre-built libraries for the FT4222H USB I/O chip.
29 Libraries are built for several target architecture variants and packaged in
32 ├── build-arm-hisiv300
34 ├── build-arm-v5-sf
[all …]
|
| /openbmc/linux/drivers/watchdog/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 on-line as fast as possible after a lock-up. There's both a watchdog
21 <file:Documentation/watchdog/watchdog-api.rst> in the kernel source.
51 bool "Update boot-enabled watchdog until userspace takes over"
77 bool "Enable watchdog hrtimer-based pretimeouts"
114 event put the kernel into panic.
204 This driver can also be built as a module. If so, the module
215 This driver can be built as a module. The module name is da9063_wdt.
225 This driver can be built as a module. The module name is da9062_wdt.
228 tristate "Watchdog device controlled through GPIO-line"
[all …]
|
| /openbmc/openbmc/meta-security/meta-parsec/ |
| H A D | README.md | 1 meta-parsec layer
11 URI: git://git.openembedded.org/meta-openembedded
14 URI git://git.yoctoproject.org/meta-security
17 URI https://github.com/kraj/meta-clang.git
20 Adding the meta-parsec layer to your build
26 location of the meta-parsec layer to bblayers.conf, along with any
31 /path/to/yocto/meta-yocto \
32 /path/to/yocto/meta-yocto-bsp \
33 /path/to/meta-openembedded/meta-oe \
34 /path/to/meta-openembedded/meta-python \
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | incompatible_lic.py | 4 # SPDX-License-Identifier: MIT
17 result = bitbake('%s --dry-run' % (pn), ignore_status=True)
21 # Verify that a package with an SPDX license cannot be built when
25 …self.lic_test('incompatible-license', 'GPL-3.0-only', 'GPLv3', "is an obsolete license, please use…
27 # Verify that a package with an SPDX license cannot be built when
31 …self.lic_test('incompatible-license', 'GPL-3.0-only', '*GPLv3', "*GPLv3 is an invalid license wild…
34 # license cannot be built when INCOMPATIBLE_LICENSE contains this alias
36 …self.lic_test('incompatible-license-alias', 'GPL-3.0-only', 'GPLv3', "is an obsolete license, plea…
39 # license cannot be built when INCOMPATIBLE_LICENSE contains a wildcarded
42 …self.lic_test('incompatible-license-alias', 'GPL-3.0-only', '*GPL-3.0', "*GPL-3.0 is an invalid li…
[all …]
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A 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
|
| /openbmc/linux/certs/ |
| H A D | system_keyring.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
16 #include <keys/asymmetric-type.h>
36 * restrict_link_by_builtin_trusted - Restrict keyring addition by built-in CA
42 * Restrict the addition of keys into a keyring based on the key-to-be-added
43 * being vouched for by a key in the built in system keyring.
55 * restrict_link_by_digsig_builtin - Restrict digitalSignature key additions by the built-in keyring
61 * Restrict the addition of keys into a keyring based on the key-to-be-added
62 * being vouched for by a key in the built in system keyring. The new key
76 * restrict_link_by_builtin_and_secondary_trusted - Restrict keyring
77 * addition by both built-in and secondary keyrings.
[all …]
|
| /openbmc/linux/drivers/net/wireless/intel/ipw2x00/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
34 rather than built-in (Y). This driver requires firmware at device
35 initialization time, and when built-in this typically happens
38 this driver into your kernel image, you can avoid this problem by
46 With this feature compiled into the driver, you can switch to
96 rather than built-in (Y). This driver requires firmware at device
97 initialization time, and when built-in this typically happens
100 this driver into your kernel image, you can avoid this problem by
108 With this feature compiled into the driver, you can switch to
132 % tethereal -i rtap0
|
| /openbmc/linux/drivers/nvmem/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
22 read/write directly into nvmem.
37 calibration data required for the PCIe or the USB-C PHY.
39 This driver can also be built as a module. If so, the module will
40 be called nvmem-apple-efuses.
43 tristate "Broadcom On-Chip OTP Controller support"
51 This driver can also be built as a module. If so, the module
52 will be called nvmem-bcm-ocotp.
71 This driver can also be built as a module. If so, the module
72 will be called nvmem-imx-iim.
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.u-boot_on_efi | 1 # SPDX-License-Identifier: GPL-2.0+
5 U-Boot on EFI
7 This document provides information about U-Boot running on top of EFI, either
8 as an application or just as a means of getting U-Boot onto a new platform.
22 32/64-bit
28 ----------
29 Running U-Boot on EFI is useful in several situations:
31 - You have EFI running on a board but U-Boot does not natively support it
32 fully yet. You can boot into U-Boot from EFI and use that until U-Boot is
35 - You need to use an EFI implementation (e.g. UEFI) because your vendor
[all …]
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/driver-api/early-userspace/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/scsi/ |
| H A 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.
|
| /openbmc/linux/Documentation/trace/coresight/ |
| H A 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 …]
|
| /openbmc/openbmc/poky/meta/conf/ |
| H A D | documentation.conf | 3 # Mail your changes to openembedded-devel@openembedded.org
8 do_build[doc] = "Default task for a recipe - depends on all other normal tasks required to 'build' …
16 do_compile_ptest_base[doc] = "Compiles the runtime test suite included in the software being built"
17 …the source by enabling and disabling any build-time and configuration options for the software bei…
18 …onfigure_ptest_base[doc] = "Configures the runtime test suite included in the software being built"
26 do_kernel_checkout[doc] = "Checks out source/meta branches for a linux-yocto style kernel"
27 do_kernel_configcheck[doc] = "Validates the kernel configuration for a linux-yocto style kernel"
28 do_kernel_configme[doc] = "Assembles the kernel configuration for a linux-yocto style kernel"
32 do_package[doc] = "Analyzes the content of the holding area and splits it into subsets based on ava…
43 do_populate_sysroot[doc] = "Copies a subset of files installed by do_install into the sysroot in or…
[all …]
|
| /openbmc/phosphor-mrw-tools/docs/ |
| H A D | mrw-xml-requirements.md | 5 [Serverwiz2](https://www.github.com/open-power/serverwiz). The requirements in
14 contains all FRUs (field replaceable units), along with a few non-FRU entities,
19 - Set the `FRU_NAME` attribute of that target.
28 modeled in the MRW XML. For a system built with parts that already have existing
35 data that is either already built into the XML representations of the existing
50 All of the BMC chip attributes that are needed for the device tree are pre-built
51 into the XML representation and don't need to be updated when the device is
52 placed into a system in Serverwiz.
61 spi-master-unit on the BMC that has its `SPI_FUNCTION` attribute set to
95 Set to the logic value required to activate the LED - either 0 or 1. The default
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | extensible.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
12 hardware, and ease integration into the rest of the
17 For a side-by-side comparison of main features supported for an
19 :ref:`sdk-manual/intro:introduction` section.
24 ":ref:`sdk-manual/working-projects:using the sdk toolchain directly`" chapter
30 The extensible SDK provides a cross-development toolchain and libraries
45 --------------------------------------
61 benefit of having a single, self-contained archive that includes all the
63 need to provide a well-functioning binary artefact cache over the network
69 -------------------------------------------------------------------
[all …]
|
| /openbmc/linux/Documentation/driver-api/rapidio/ |
| H A 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 …]
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | understand-autobuilder.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
10 The "a-full" and "a-quick" targets are the usual entry points into the
21 within the :yocto_git:`yocto-autobuilder-helper </yocto-autobuilder-helper>`
23 example could be ``qemux86-64`` which looks like::
25 "qemux86-64" : {
26 "MACHINE" : "qemux86-64",
27 "TEMPLATE" : "arch-qemu",
35 And to expand that, you need the ``arch-qemu`` entry from
38 "arch-qemu" : {
42 …"BBTARGETS" : "core-image-sato core-image-sato-dev core-image-sato-sdk core-image-minimal core-ima…
[all …]
|