| /openbmc/qemu/docs/devel/ |
| H A D | kconfig.rst | 13 SCSI adapters. Arm, s390 and x86 boards can all present a virtio-blk
16 Each QEMU target enables a subset of the boards, devices and buses that
21 QEMU uses a simple domain-specific language to describe the dependencies
24 * new targets and boards can be added without knowing in detail the
27 include all the required dependencies and all the devices that the
30 * users can easily build reduced versions of QEMU that support only a subset
31 of boards or devices. For example, by default most targets will include
32 all emulated PCI devices that QEMU supports, but the build process is
36 This domain-specific language is based on the Kconfig language that
41 is instead specified in per-target files under the ``default-configs/``
[all …]
|
| /openbmc/u-boot/common/spl/ |
| H A D | Kconfig | 17 If you want to build SPL as well as the normal image, say Y.
22 default y
25 supports MMC, NAND and YMODEM and other methods loading of U-Boot
29 bool "Pass hand-off information from SPL to U-Boot proper"
32 It is useful to be able to pass information from SPL to U-Boot
33 proper to preserve state that is known in SPL and is needed in U-Boot.
34 Enable this to locate the handoff information in U-Boot proper, early
35 in boot. It is available in gd->handoff. The state state is set up
44 This option can minilize the SPL size to compatible with AST2600-A0
48 bool "Pass hand-off information from SPL to U-Boot proper"
[all …]
|
| /openbmc/qemu/.gitlab-ci.d/custom-runners/ |
| H A D | ubuntu-22.04-aarch64.yml | 1 # All ubuntu-22.04 jobs should run successfully in an environment
2 # setup by the scripts/ci/setup/ubuntu/build-environment.yml task
3 # "Install basic packages to build QEMU on Ubuntu 22.04"
5 ubuntu-22.04-aarch64-all-linux-static:
8 stage: build
10 - ubuntu_22.04
11 - aarch64
13 - if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/'
14 - if: "$AARCH64_RUNNER_AVAILABLE"
16 - mkdir build
[all …]
|
| /openbmc/linux/drivers/scsi/aic7xxx/ |
| H A D | Kconfig.aic79xx | 1 # SPDX-License-Identifier: GPL-2.0-only
4 # $Id: //depot/linux-aic79xx-2.5.0/drivers/scsi/aic7xxx/Kconfig.aic79xx#4 $
11 This driver supports all of Adaptec's Ultra 320 PCI-X
17 default "32"
24 vary this number based on device behavior. For devices with a
28 Due to resource allocation issues in the Linux SCSI mid-layer, using
30 failures when many devices are attached to the system. For this reason,
31 the default is set to 32. Higher values may result in higher performance
32 on some devices. The upper bound is 253. 0 disables tagged queueing.
38 int "Initial bus reset delay in milli-seconds"
[all …]
|
| H A D | Kconfig.aic7xxx | 1 # SPDX-License-Identifier: GPL-2.0-only
4 # $Id: //depot/linux-aic79xx-2.5.0/drivers/scsi/aic7xxx/Kconfig.aic7xxx#7 $
7 tristate "Adaptec AIC7xxx Fast -> U160 support"
22 default "32"
29 vary this number based on device behavior. For devices with a
33 Due to resource allocation issues in the Linux SCSI mid-layer, using
35 failures when many devices are attached to the system. For this reason,
36 the default is set to 32. Higher values may result in higher performance
37 on some devices. The upper bound is 253. 0 disables tagged queueing.
43 int "Initial bus reset delay in milli-seconds"
[all …]
|
| /openbmc/linux/drivers/base/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
12 Before the switch to the netlink-based uevent source, this was
19 it is known to create out-of-memory situations during bootup.
24 default ""
26 To disable user space helper program execution at by default
36 nodes with their default names and permissions for all
37 registered devices with an assigned major/minor number.
44 functional /dev without any further help. It also allows simple
73 with the PROT_EXEC flag. This can break, for example, non-KMS
77 bool "Select only drivers that don't need compile-time external firmware"
[all …]
|
| /openbmc/linux/arch/xtensa/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
58 Xtensa processors are 32-bit RISC machines designed by Tensilica
63 a home page at <http://www.linux-xtensa.org/>.
82 default 100
99 default 0x6e400000
102 def_bool $(success,test "$(shell,echo __XTENSA_EB__ | $(CC) -E -P -)" = 1)
108 …def_bool $(success,test "$(shell,echo __XTENSA_CALL0_ABI__ | $(CC) -mabi=call0 -E -P - 2>/dev/null…
114 default XTENSA_VARIANT_FSF
117 bool "fsf - default (not generic) configuration"
121 bool "dc232b - Diamond 232L Standard Core Rev.B (LE)"
[all …]
|
| /openbmc/openbmc/poky/meta-yocto-bsp/ |
| H A D | README.hardware.md | 13 Support for additional devices is normally added by adding BSP layers to your
15 (BSP) Developer's Guide - documentation source is in documentation/bspguide or
18 Note that these reference BSPs use the linux-yocto kernel and in general don't
26 The following boards are supported by the meta-yocto-bsp layer:
28 * Texas Instruments Beaglebone (`beaglebone-yocto`)
29 * General 64-bit Arm SystemReady platforms (`genericarm64`)
30 * General IA platforms (`genericx86` and `genericx86-64`)
38 Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/
44 git send-email -M -1 --to poky@lists.yoctoproject.org
46 Send pull requests, patches, comments or questions about meta-yocto-bsp to
[all …]
|
| /openbmc/openbmc/poky/ |
| H A D | README.hardware.md | 13 Support for additional devices is normally added by adding BSP layers to your
15 (BSP) Developer's Guide - documentation source is in documentation/bspguide or
18 Note that these reference BSPs use the linux-yocto kernel and in general don't
26 The following boards are supported by the meta-yocto-bsp layer:
28 * Texas Instruments Beaglebone (`beaglebone-yocto`)
29 * General 64-bit Arm SystemReady platforms (`genericarm64`)
30 * General IA platforms (`genericx86` and `genericx86-64`)
38 Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/
44 git send-email -M -1 --to poky@lists.yoctoproject.org
46 Send pull requests, patches, comments or questions about meta-yocto-bsp to
[all …]
|
| /openbmc/linux/arch/um/drivers/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 menu "UML Character Devices"
7 default y
14 The User-Mode Linux environment allows you to create virtual serial
18 See <http://user-mode-linux.sourceforge.net/old/input.html> for more
44 lines to host pseudo-terminals. Access to both traditional
45 pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
46 with this option. The assignment of UML devices to host devices
55 (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
68 string "xterm channel default terminal emulator"
[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 ----------
53 All devices are presented in the RapidIO subsystem by corresponding rio_dev data
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
[all …]
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | fuzzing.rst | 5 This document describes the virtual-device fuzzing infrastructure in QEMU and
9 ------
16 is an *in-process* fuzzer. For the developer, this means that it is their
17 responsibility to ensure that state is reset between fuzzing-runs.
20 --------------------
22 To build the fuzzers, install a recent version of clang:
24 Here, enable-asan and enable-ubsan are optional but they allow us to reliably
25 detect bugs such as out-of-bounds accesses, uses-after-free, double-frees
28 CC=clang-8 CXX=clang++-8 /path/to/configure \
29 --enable-fuzzing --enable-asan --enable-ubsan
[all …]
|
| /openbmc/qemu/docs/system/riscv/ |
| H A D | virt.rst | 8 real-world hardware.
10 Supported devices
11 -----------------
13 The ``virt`` machine supports the following devices:
17 * Platform-Level Interrupt Controller (PLIC)
22 * 8 virtio-mmio transport devices
26 The hypervisor extension has been enabled for the default CPU, so virtual
27 machines with hypervisor extension can simply be used without explicitly
31 ----------------------------------
34 which it passes to the guest, if there is no ``-dtb`` option. This provides
[all …]
|
| /openbmc/u-boot/arch/x86/ |
| H A D | Kconfig | 5 default "x86"
8 prompt "Run U-Boot in 32/64-bit mode"
9 default X86_RUN_32BIT
11 U-Boot can be built as a 32-bit binary which runs in 32-bit mode
12 even on 64-bit machines. In this case SPL is not used, and U-Boot
13 runs directly from the reset vector (via 16-bit start-up).
15 Alternatively it can be run as a 64-bit binary, thus requiring a
16 64-bit machine. In this case SPL runs in 32-bit mode (via 16-bit
17 start-up) then jumps to U-Boot in 64-bit mode.
19 For now, 32-bit mode is recommended, as 64-bit is still
[all …]
|
| /openbmc/qemu/ |
| H A D | configure | 14 source_path=$(cd "$(dirname -- "$0")"; pwd)
16 if test "$PWD" -ef "$source_path"
18 echo "Using './build' as the directory for build output"
20 MARKER=build/auto-created-by-configure
22 if test -e build
24 if test -f $MARKER
26 rm -rf build
28 echo "ERROR: ./build dir already exists and was not previously created by configure"
33 if ! mkdir build || ! touch $MARKER
35 echo "ERROR: Could not create ./build directory. Check the permissions on"
[all …]
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | qpl-compression.rst | 4 The Intel Query Processing Library (Intel ``QPL``) is an open-source library to
8 The ``QPL`` compression relies on Intel In-Memory Analytics Accelerator(``IAA``)
21 +----------------+ +------------------+
22 | MultiFD Thread | |accel-config tool |
23 +-------+--------+ +--------+---------+
27 +-------+--------+ | Setup IAA
29 +-------+---+----+ |
31 | +-------------+-------+
33 | Devices +-----+-----+
35 | +-----+-----+
[all …]
|
| H A D | uadk-compression.rst | 4 UADK is a general-purpose user space accelerator framework that uses shared
8 UADK includes Unified/User-space-access-intended Accelerator Framework (UACCE),
24 different character devices with UACCE by using kernel-mode drivers of the
25 vendors. A user can access the hardware accelerators by performing user-mode
26 operations on the character devices.
30 +----------------------------------+
32 +----+------------------------+----+
35 +-------+--------+ +-------+-------+
37 +-------+--------+ +-------+-------+
41 | +--------+------+
[all …]
|
| /openbmc/linux/drivers/usb/gadget/legacy/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
23 # Gadget drivers are hardware-neutral, or "platform independent",
44 Gadget Zero is a two-configuration device. It either sinks and
47 conformance. The driver needs only two bulk-capable endpoints, so
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | runtime-testing.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
6 The OpenEmbedded build system makes available a series of automated
15 Yocto Project, see the ":ref:`ref-manual/release-process:testing and quality assurance`"
27 ------------------------------
31 - *Set up to avoid interaction with sudo for networking:* To
34 - Add ``NOPASSWD`` for your user in ``/etc/sudoers`` either for all
35 commands or just for ``runqemu-ifup``. You must provide the full
44 - Manually configure a tap interface for your system.
46 - Run as root the script in ``scripts/runqemu-gen-tapdevs``, which
47 should generate a list of tap devices. This is the option
[all …]
|
| /openbmc/linux/drivers/usb/gadget/udc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
21 # before discrete ones so they will be the initial/default value:
22 # - integrated/SOC controllers first
23 # - licensed IP used in both SOC and discrete versions
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.x86 | 1 # SPDX-License-Identifier: GPL-2.0+
6 U-Boot on x86
9 This document describes the information about U-Boot running on x86 targets,
10 including supported boards, build instructions, todo list, etc.
13 ------
14 U-Boot supports running as a coreboot [1] payload on x86. So far only Link
17 most of the low-level details.
19 U-Boot is a main bootloader on Intel Edison board.
21 U-Boot also supports booting directly from x86 reset vector, without coreboot.
23 'bare metal', U-Boot acts like a BIOS replacement. The following platforms
[all …]
|
| /openbmc/u-boot/ |
| H A D | README | 1 # SPDX-License-Identifier: GPL-2.0+
3 # (C) Copyright 2000 - 2013
9 This directory contains the source code for U-Boot, a boot loader for
15 The development of U-Boot is closely related to Linux: some parts of
37 scattered throughout the U-Boot source identifying the people or
41 actual U-Boot source tree; however, it can be created dynamically
51 U-Boot, you should send a message to the U-Boot mailing list at
52 <u-boot@lists.denx.de>. There is also an archive of previous traffic
53 on the mailing list - please search the archive before asking FAQ's.
54 Please see http://lists.denx.de/pipermail/u-boot and
[all …]
|
| /openbmc/qemu/docs/ |
| H A D | pcie_pci_bridge.txt | 6 PCIE-to-PCI bridge is a new method for legacy PCI
9 Previously Intel DMI-to-PCI bridge was used for this purpose.
10 But due to its strict limitations - no support of hot-plug,
11 no cross-platform and cross-architecture support - a new generic
12 PCIE-to-PCI bridge should now be used for any legacy PCI device usage
15 This generic PCIE-PCI bridge is a cross-platform device,
16 can be hot-plugged into appropriate root port (requires additional actions,
17 see 'PCIE-PCI bridge hot-plug' section),
18 and supports devices hot-plug into the bridge itself
21 Hot-plug of legacy PCI devices into the bridge
[all …]
|
| /openbmc/linux/fs/erofs/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
9 EROFS (Enhanced Read-Only File System) is a lightweight read-only
11 xattrs/data, chunk-based deduplication, multiple devices, etc.) for
12 scenarios which need high-performance read-only solutions, e.g.
13 smartphones with Android OS, LiveCDs and high-density hosts with
16 It also provides fixed-sized output compression support in order to
18 ratios and implements in-place decompression to reuse the file page
20 quite useful to ensure guaranteed end-to-end runtime decompression
21 performance under extremely memory pressure without extra cost.
34 which can be used for Android eng build, for example.
[all …]
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | building.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 distribution-specific source file or via the Kernel's main git tree\ [1]_.
12 - you're a braveheart and want to experiment with new stuff;
13 - if you want to report a bug;
14 - if you're developing new patches
23 https://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
50 Device Drivers --->
51 <M> Remote Controller support --->
54 [*] HDMI CEC drivers --->
55 <*> Multimedia support --->
[all …]
|