| /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
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 ``configs/``
44 QEMU; the default configuration that QEMU ships with should be okay in
[all …]
|
| /openbmc/u-boot/drivers/mtd/ubi/ |
| H A D | Kconfig | 5 default ENV_IS_IN_UBI
11 bool "Enable UBI - Unsorted block images"
16 UBI is a software layer above MTD layer which admits of LVM-like
17 logical volumes on top of MTD devices, hides some complexities of
20 (www.linux-mtd.infradead.org).
25 int "UBI wear-leveling threshold"
26 default 4096
31 of UBI devices. When this threshold is exceeded, UBI starts performing
35 The default value should be OK for SLC NAND flashes, NOR flashes and
36 other flashes which have eraseblock life-cycle 100000 or more.
[all …]
|
| /openbmc/qemu/docs/system/s390x/ |
| H A D | bootdevices.rst | 1 Boot devices on s390x
5 --------------------------------
9 in s390x-speak -- IPL means "Initial Program Load").
15 qemu-system-s390x -drive if=none,id=dr1,file=guest.qcow2 \
16 -device virtio-blk,drive=dr1,bootindex=1
18 Multiple devices may have a bootindex. The lowest bootindex is assigned to the
21 remaining boot devices to try.
23 For booting from a CD-ROM ISO image (which needs to include El-Torito boot
24 information in order to be bootable), it is recommended to specify a ``scsi-cd``
27 qemu-system-s390x -blockdev file,node-name=c1,filename=... \
[all …]
|
| H A D | css.rst | 5 functionless) channel paths, and channel devices (virtio-ccw, 3270, and
6 devices passed via vfio-ccw). It supports multiple subchannel sets (MSS) and
7 multiple channel subsystems extended (MCSS-E).
9 All channel devices support the ``devno`` property, which takes a parameter
12 The default channel subsystem image id (``<cssid>``) is ``0xfe``. Devices in
14 enable MCSS-E. Note that devices with a different cssid will not be visible
15 if the guest OS does not enable MCSS-E (which is true for all supported guest
18 Supported values for the subchannel set id (``<ssid>``) range from ``0-3``.
19 Devices with a ssid that is not ``0`` will not be visible if the guest OS
24 The device number can range from ``0-0xffff``.
[all …]
|
| /openbmc/qemu/docs/system/i386/ |
| H A D | microvm.rst | 7 It's a minimalist machine type without ``PCI`` nor ``ACPI`` support,
8 designed for short-lived guests. microvm also establishes a baseline
13 Supported devices
14 -----------------
16 The microvm machine type supports the following devices:
18 - ISA bus
19 - i8259 PIC (optional)
20 - i8254 PIT (optional)
21 - MC146818 RTC (optional)
22 - One ISA serial port (optional)
[all …]
|
| /openbmc/u-boot/drivers/serial/ |
| H A D | Kconfig | 8 int "Default baudrate"
9 default 115200
11 Select a default baudrate, where "default" has a driver-specific
13 in the SPL stage (most drivers) or for choosing a default baudrate
18 # Running without a serial console is not supported by the
19 # non-dm serial code
21 default y
24 during serial port initialization (default y). Set this to n on
29 default y if !DM_SERIAL || (SPL && !SPL_DM_SERIAL) || \
32 In various cases, we need to specify which of the UART devices that
[all …]
|
| /openbmc/u-boot/include/ |
| H A D | tca642x.h | 13 * but WITHOUT ANY WARRANTY; without even the implied warranty of
20 * MA 02111-1307 USA
43 /* Default to an address that hopefully won't corrupt other i2c devices */
48 /* Default to an address that hopefully won't corrupt other i2c devices */
|
| /openbmc/qemu/docs/ |
| H A D | qdev-device-use.txt | 1 = How to convert to -device & friends =
5 In qdev, each device has a parent bus. Some devices provide one or
7 -device parameter bus.
10 where this address can be configured, devices provide a bus-specific
16 SCSI scsi-id %u
19 virtio-serial-bus nr %u
20 ccid-bus slot %u
23 Example: device i440FX-pcihost is on the root bus, and provides a PCI
24 bus named pci.0. To put a FOO device into its slot 4, use -device
25 FOO,bus=/i440FX-pcihost/pci.0,addr=4. The abbreviated form bus=pci.0
[all …]
|
| 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/qemu/docs/system/ |
| H A D | introduction.rst | 7 ---------------------------
10 memory and emulated devices) to run a guest OS. It supports a number
14 .. list-table:: Supported Accelerators
15 :header-rows: 1
17 * - Accelerator
18 - Host OS
19 - Host Architectures
20 * - KVM
21 - Linux
22 - Arm (64 bit only), MIPS, PPC, RISC-V, s390x, x86
[all …]
|
| /openbmc/u-boot/drivers/video/ |
| H A D | Kconfig | 11 This enables driver model for LCD and video devices. These support
13 to display a command-line console or splash screen. Enabling this
20 default y
24 This driver can be use with "simple-panel" and
26 (leds/backlight/pwm-backlight.txt)
34 This driver can be used with "simple-panel" and
36 (leds/backlight/gpio-backlight.txt)
39 bool "Support 8-bit-per-pixel displays"
41 default y if DM_VIDEO
43 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-navigation/gpsd/gpsd/ |
| H A D | gpsd.init | 4 # Required-Start: $remote_fs $syslog $network
5 # Should-Start: bluetooth dbus udev
6 # Required-Stop: $remote_fs $syslog $network
7 # Should-Stop:
8 # Default-Start: 2 3 4 5
9 # Default-Stop: 0 1 6
10 # X-Start-Before: ntp
11 # Short-Description: GPS (Global Positioning System) daemon start/stop script
13 # which is able to monitor one or more GPS devices
31 [ -x "$DAEMON" ] || exit 0
[all …]
|
| /openbmc/u-boot/dts/ |
| H A D | Kconfig | 26 bool "Run-time configuration via Device Tree"
29 This feature provides for run-time configuration of U-Boot
33 bool "Board-specific manipulation of Device Tree"
36 U-Boot's device tree (e.g. to delete device from it). This option
37 make the Device Tree writeable and provides a board-specific
38 "board_fix_fdt" callback (called during pre-relocation time), which
40 modified copy is subsequently used by U-Boot after relocation.
43 bool "Enable run-time configuration via Device Tree in SPL"
46 Some boards use device tree in U-Boot but only have 4KB of SRAM
48 allow such boards to be supported by U-Boot SPL.
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/lvm2/files/ |
| H A D | lvm.conf | 2 # It contains the default settings that would be used if there was no
11 # This section allows you to configure which block devices should
13 devices {
22 # A filter that tells LVM2 to only use a restricted set of devices.
27 # the device will be accepted or rejected (ignored). Devices that
40 # If it doesn't do what you expect, check the output of 'vgscan -vvvv'.
43 # By default we accept every block device:
49 # When testing I like to work with just loopback devices:
59 # rescanning dud devices (which can take a very long time). By
60 # default this cache file is hidden in the /etc/lvm directory.
[all …]
|
| /openbmc/u-boot/drivers/bootcount/ |
| H A D | Kconfig | 15 default BOOTCOUNT_AM33XX if AM33XX || SOC_DA8XX
16 default BOOTCOUNT_AT91 if AT91SAM9XE
17 default BOOTCOUNT_GENERIC
20 bool "Generic default boot counter"
74 bool "Boot counter in a device-model device"
76 Enables reading/writing the bootcount in a device-model based
77 backing store. If an entry in /chosen/u-boot,bootcount-device
85 menu "Backing stores for device-model backed bootcount"
87 bool "Support RTC devices as a backing store for bootcount"
92 'u-boot,bootcount-rtc' and the 'rtc'-property (a phandle pointing
[all …]
|
| /openbmc/u-boot/common/spl/ |
| H A D | Kconfig | 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"
50 default y
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-security/usbguard/ |
| H A D | usbguard_1.1.3.bb | 3 # SPDX-License-Identifier: MIT
5 SUMMARY = "USBGuard daemon for blacklisting and whitelisting of USB devices"
7 rogue USB devices (a.k.a. Bad USB) by implementing basic whitelisting and blacklisting \
8 capabilities based on device attributes. This recipe takes OpenSSL as crypto-backend for \
11 LICENSE = "GPL-2.0-only"
14 SRC_URI = "https://github.com/USBGuard/usbguard/releases/download/${BPN}-${PV}/${BPN}-${PV}.tar.gz \
15 file://0001-Add-and-use-pkgconfig-instead-of-libgcrypt-config.patch \
16 file://0001-Adapt-for-protobuf-30.0-API-changes.patch \
21 inherit autotools-brokensep bash-completion pkgconfig systemd github-releases
23 DEPENDS = "glib-2.0-native libcap-ng libqb libxml2-native libxslt-native protobuf protobuf-native x…
[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.
21 **Note**: The BMC and cores will be automatically added without the need to set
27 to be generated, all of the corresponding devices and connections must be
50 All of the BMC chip attributes that are needed for the device tree are pre-built
61 spi-master-unit on the BMC that has its `SPI_FUNCTION` attribute set to
74 NCSI. The default is 0.
79 hardware checksum enabled, or 0 if not enabled. The default is 1.
95 Set to the logic value required to activate the LED - either 0 or 1. The default
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/zeroconf/ |
| H A D | zeroconf_0.9.bb | 1 SUMMARY = "IPv4 link-local address allocator"
3 link-local addresses. IPv4 link-local addresses are useful when setting \
4 up ad-hoc networking between devices without the involvement of a either \
11 LICENSE = "GPL-2.0-or-later"
17 SRC_URI = "http://www.progsoc.org/~wildfire/zeroconf/download/${BPN}-${PV}.tar.gz \
19 file://makefile-add-ldflags.patch \
20 file://zeroconf-default \
21 file://debian-zeroconf \
22 file://0001-zeroconf-Rename-arp_op-to-avoid-namespace-conflicts-.patch \
31 install -d ${D}${sbindir}
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | chassis.hpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
40 * the BMC. Small and mid-sized systems may contain a single chassis. In a
41 * large rack-mounted system, each drawer may correspond to a chassis.
49 // Specify which compiler-generated methods we want
55 ~Chassis() = default;
64 * @param inventoryPath D-Bus inventory path for this chassis
65 * @param devices Devices within this chassis, if any. The vector should
66 * contain regulator devices and any related devices required
70 std::vector<std::unique_ptr<Device>> devices = in Chassis() argument
[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
5 ubuntu-22.04-aarch64-all-linux-static:
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
17 - cd build
18 # Disable -static-pie due to build error with system libc:
[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/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_fru_device.robot | 45 ${ipmi_fru}= Get IPMI FRU Devices Data ${ipmi_output}
51 ${dbus_fru_uri_list}= Fetch DBUS URI List Without Unicode ${dbus_fru_uri}
54 Get DBUS Dictionary For FRU Devices ${dbus_fru_uri_list} ${ipmi_fru}
71 # Compare read FRU data Count returned -- count is ‘1’ based, with inventory area count.
88 # Verify response for invalid response data - extra bytes.
96 [Setup] Get Default FRU Data
97 [Teardown] Restore Default FRU Data
120 [Setup] Get Default FRU Data
121 [Teardown] Restore Default FRU Data
149 Get IPMI FRU Devices Data
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/src/ |
| H A D | ucd90x_device.hpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
35 * PMBusDriverDevice sub-class for the UCD90X family of power sequencer devices.
37 * These devices share a common device driver.
42 // Specify which compiler-generated methods we want
48 virtual ~UCD90xDevice() = default;
69 * This is a manufacturer-specific command that replaces the standard
70 * STATUS_MFR_SPECIFIC command on UCD90x devices.
72 * The returned value is in host-endian order.
76 * command value are page-specific. However, the current device driver only
[all …]
|