| /openbmc/u-boot/board/freescale/mpc8610hpcd/ |
| H A D | mpc8610hpcd_diu.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Copyright 2007-2011 Freescale Semiconductor, Inc.
22 volatile ccsr_gur_t *gur = &immap->im_gur; in diu_set_pixel_clock()
23 volatile unsigned int *guts_clkdvdr = &gur->clkdvdr; in diu_set_pixel_clock()
47 temp = in_8(&pixis->brdcfg0); in platform_diu_init()
50 /* Dual link LVDS */ in platform_diu_init()
53 name = "Dual-Link LVDS"; in platform_diu_init()
55 /* Single link LVDS */ in platform_diu_init()
57 name = "Single-Link LVDS"; in platform_diu_init()
60 if (in_8(&pixis->ver) == 1) /* Board version */ in platform_diu_init()
[all …]
|
| /openbmc/qemu/qapi/ |
| H A D | cxl.json | 1 # -*- Mode: Python -*-
34 # @cxl-inject-general-media-event:
44 # @flags: Event Record Flags. See CXL r3.0 Table 8-42 Common Event
48 # lower bits include some flags. See CXL r3.0 Table 8-43 General
52 # information. See CXL r3.0 Table 8-43 General Media Event
55 # @type: Type of memory event that occurred. See CXL r3.0 Table 8-43
59 # @transaction-type: Type of first transaction that caused the event
60 # to occur. See CXL r3.0 Table 8-43 General Media Event Record,
72 # @component-id: Device specific component identifier for the event.
73 # May describe a field replaceable sub-component of the device.
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | NetworkAdapter.v1_13_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
104 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
106 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
122 …"description": "The link to the software inventory resource that represents the active firmware im…
123 …"longDescription": "This property shall contain a link to a resource of type `SoftwareInventory` t…
[all …]
|
| H A D | PortMetrics.v1_8_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
31 "description": "The available OEM-specific actions for this resource.",
32 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
42 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
58 …"longDescription": "This property shall contain CXL Specification-defined 'Backpressure Average Pe…
69 "description": "The Fibre Channel-specific port metrics for network ports.",
70 … "longDescription": "This type shall describe Fibre Channel-specific metrics for network ports.",
72 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| H A D | IPAddresses.v1_1_5.json | 3 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
4 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
14 …ddress is currently within its valid lifetime but is now outside its RFC4862-defined preferred lif…
16 …"Preferred": "This address is currently within both its RFC4862-defined valid and preferred lifeti…
26 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
42 …igned to this interface. If DHCPv4 is enabled on the interface, this property becomes read-only.",
43 "pattern": "^(?:[0-9]{1,3}\\.){3}[0-9]{1,3}$",
65 …address, this property becomes read-only. If multiple IPv4 addresses are present on the same inte…
66 "pattern": "^(?:[0-9]{1,3}\\.){3}[0-9]{1,3}$",
76 …operties contained in this object shall conform to the Redfish Specification-described requirement…
[all …]
|
| H A D | ComponentIntegrity.v1_3_2.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
43 …"longDescription": "This object shall contain common identity-related authentication information.",
45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
61 … "description": "A link to the certificate that represents the identity of the component.",
62 …"longDescription": "This property shall contain a link to a resource of type `Certificate` that re…
86 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| H A D | Control.v1_7_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
31 "description": "The available OEM-specific actions for this resource.",
32 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
42 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
57 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
60 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/etag"
63 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/id"
66 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/type"
[all …]
|
| H A D | Processor.v1_21_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
57 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
95 …operties contained in this object shall conform to the Redfish Specification-described requirement…
106 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
177 …operties contained in this object shall conform to the Redfish Specification-described requirement…
214 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| /openbmc/u-boot/scripts/ |
| H A D | Makefile.host | 1 # SPDX-License-Identifier: GPL-2.0
10 # hostprogs-y := bin2hex
13 # hostprogs-y := lxdialog
14 # lxdialog-objs := checklist.o lxdialog.o
15 # Will compile lxdialog.c and checklist.c, and then link the executable
18 # hostprogs-y := qconf
19 # qconf-cxxobjs := qconf.o
20 # qconf-objs := menu.o
24 __hostprogs := $(sort $(hostprogs-y) $(hostprogs-m))
27 # Executables compiled from a single .c file
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | Chassis.interface.yaml | 5 - name: Type
12 - name: ChassisType
16 - name: Blade
18 An enclosed or semi-enclosed, typically vertically-oriented,
19 system chassis that must be plugged into a multi-system chassis
21 - name: Component
25 - name: Enclosure
29 - name: Module
33 - name: RackMount
35 A single-system chassis designed specifically for mounting in an
[all …]
|
| /openbmc/openpower-vpd-parser/ |
| H A D | README.md | 7 [at a broken link](https://www-355.ibm.com/systems/power/openpower/posting.xhtml?postingId=1D060729…
13 This is a build-time YAML driven application that parses the OpenPower VPD
14 format and uses the YAML configuration (see extra-properties-example.yaml and
17 - The supported records and keywords.
18 - How VPD data is translated into D-Bus interfaces and properties.
22 D-Bus object path(s) that EEPROM data needs to be published under.
26 This parser is can be built by passing in the `--enable-ibm-parser` configure
29 - It parses all the records and keywords from the VPD, including large keywords
31 - It relies on a runtime JSON configuration (see examples/inventory.json) to
32 determine the D-Bus object path(s) that hold interfaces and properties
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-devtools/gcc/ |
| H A D | libgcc-initial.inc | 5 # a non-threaded and non-shared compiler (gcc-cross-initial), then use
6 # that to build libgcc-initial which is used to build glibc which we can
7 # then build gcc-cross and libgcc against.
9 # We were able to drop the glibc dependency from gcc-cross, with two tweaks:
16 # Once gcc-cross is libc independent, we can use it to build both
17 # libgcc-initial and then later libgcc.
19 # libgcc-initial is tricky as we need to imitate the non-threaded and
20 # non-shared case. We can do that by hacking the threading mode back to
21 # "single" even if gcc reports "posix" and disable libc presence for the
22 # libgcc-intial build. We have to create the dummy limits.h to avoid
[all …]
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp-kernel.md | 1 # OpenBMC in-kernel MCTP
8 This document describes a kernel-based implementation of MCTP infrastructure,
9 providing a sockets-based API for MCTP communication within an OpenBMC-based
14 - The MCTP messaging API should be an obvious application of the existing POSIX
17 - Configuration should be simple for a straightforward MCTP endpoint: a single
18 network with a single local endpoint id (EID).
20 - Infrastructure should be flexible enough to allow for more complex MCTP
22 - each MCTP network (as defined by section 3.2.31 of DSP0236) may consist of
25 - multiple distinct (ie., non-bridged) networks, possibly containing
28 - multiple local EIDs on a single interface, and
[all …]
|
| /openbmc/phosphor-dbus-interfaces/ |
| H A D | requirements.md | 11 Do not over-optimize properties by selecting explicit sizes such as `uint8`
17 non-countable values prefer `uint64` or `int64`.
28 The sdbusplus implementation has built-in support for enumerations, which flow
32 In some cases it is useful to have hardware-specific or OEM values for
34 the values contained within are to be sdbusplus-enumerations of a specific
35 pattern. See the [software compatibility][software-compat] and [dump
36 interface][dump-interface] as two current examples of this.
38 [software-compat]:
39 …https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Software/…
40 [dump-interface]:
[all …]
|
| /openbmc/u-boot/cmd/ |
| H A D | jffs2.c | 1 // SPDX-License-Identifier: GPL-2.0+
10 * Kai-Uwe Bloem, Auerswald GmbH & Co KG, <linux-development@auerswald.de>
20 * Copyright 2002 SYSGO Real-Time Solutions GmbH
26 * 'partition' - keeps current partition identifier
28 * partition := <part-id>
29 * <part-id> := <dev-id>,part_num
32 * 'mtdids' - linux kernel mtd device id <-> u-boot device id mapping
36 * <idmap> := <dev-id>=<mtd-id>
37 * <dev-id> := 'nand'|'nor'|'onenand'<dev-num>
38 * <dev-num> := mtd device number, 0...
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | IPAddresses.v1_1_5.json | 3 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
4 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
14 …ddress is currently within its valid lifetime but is now outside its RFC4862-defined preferred lif…
16 …"Preferred": "This address is currently within both its RFC4862-defined valid and preferred lifeti…
26 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
42 …igned to this interface. If DHCPv4 is enabled on the interface, this property becomes read-only.",
43 "pattern": "^(?:[0-9]{1,3}\\.){3}[0-9]{1,3}$",
65 …address, this property becomes read-only. If multiple IPv4 addresses are present on the same inte…
66 "pattern": "^(?:[0-9]{1,3}\\.){3}[0-9]{1,3}$",
76 …operties contained in this object shall conform to the Redfish Specification-described requirement…
[all …]
|
| H A D | ComponentIntegrity.v1_3_2.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
43 …"longDescription": "This object shall contain common identity-related authentication information.",
45 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
61 … "description": "A link to the certificate that represents the identity of the component.",
62 …"longDescription": "This property shall contain a link to a resource of type `Certificate` that re…
86 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| H A D | Processor.v1_21_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
34 "description": "The available OEM-specific actions for this resource.",
35 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
57 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
95 …operties contained in this object shall conform to the Redfish Specification-described requirement…
106 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
177 …operties contained in this object shall conform to the Redfish Specification-described requirement…
214 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| /openbmc/qemu/docs/system/riscv/ |
| H A D | xiangshan-kunminghu.rst | 1 BOSC Xiangshan Kunminghu FPGA prototype platform (``xiangshan-kunminghu``)
3 The ``xiangshan-kunminghu`` machine is compatible with our FPGA prototype
6 XiangShan is an open-source high-performance RISC-V processor project.
7 The third generation processor is called Kunminghu. Kunminghu is a 64-bit
13 -----------------
14 The ``xiangshan-kunminghu`` machine supports the following devices:
16 * Up to 16 xiangshan-kunminghu cores
19 * Advanced Platform-Level Interrupt Controller (APLIC)
23 ------------
24 The ``xiangshan-kunminghu`` machine can start using the standard ``-bios``
[all …]
|
| /openbmc/qemu/docs/ |
| H A D | rdma.txt | 31 data copies by bypassing the host networking stack. In particular, a TCP-based
32 migration, under certain types of memory-bound workloads, may take a more
38 over Converged Ethernet) as well as Infiniband-based. This implementation of
45 installed in your environment. You should be able to successfully link
56 of RDMA migration may in fact be harmful to co-located VMs or other
65 bulk-phase round of the migration and can be enabled for extremely
66 high-performance RDMA hardware using the following command:
69 $ migrate_set_capability rdma-pin-all on # disabled by default
92 $ migrate_set_parameter max-bandwidth 40g # or whatever is the MAX of your RDMA device
96 qemu ..... -incoming rdma:host:port
[all …]
|
| /openbmc/u-boot/test/py/ |
| H A D | multiplexed_log.py | 1 # SPDX-License-Identifier: GPL-2.0
3 # Copyright (c) 2015-2016, NVIDIA CORPORATION. All rights reserved.
5 # Generate an HTML-formatted log file containing multiple streams of data,
6 # each represented in a well-delineated/-structured fashion.
17 """A file-like object used to write a single logical stream of data into
27 chained_file: The file-like object to which all stream data should be
39 """Dummy function so that this class is "file-like".
56 stream, or was implicitly generated. A valid use-case is to
84 """A utility object used to execute sub-processes and log their output to
93 name: The name of this log stream or sub-process.
[all …]
|
| /openbmc/u-boot/drivers/pci/ |
| H A D | pcie_xilinx.c | 1 // SPDX-License-Identifier: GPL-2.0
15 * struct xilinx_pcie - Xilinx PCIe controller state
27 * pcie_xilinx_link_up() - Check whether the PCIe link is up
30 * Checks whether the PCIe link for the given device is up or down.
32 * Return: true if the link is up, else false
36 uint32_t pscr = __raw_readl(pcie->cfg_base + XILINX_PCIE_REG_PSCR); in pcie_xilinx_link_up()
42 * pcie_xilinx_config_address() - Calculate the address of a config access
55 * Return: 0 on success, else -ENODEV
67 return -ENODEV; in pcie_xilinx_config_address()
70 * Busses 0 (host-PCIe bridge) & 1 (its immediate child) are in pcie_xilinx_config_address()
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | NetworkAdapter_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: NetworkAdapter v1.13.0 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2025 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
|
| /openbmc/qemu/tests/unit/ |
| H A D | test-io-channel-tls.c | 26 #include "crypto-tls-x509-helpers.h"
27 #include "io/channel-tls.h"
28 #include "io/channel-socket.h"
29 #include "io-channel-helpers.h"
37 #define WORKDIR "tests/test-io-channel-tls-work/"
38 #define KEYFILE WORKDIR "key-ctx.pem"
61 data->finished = true; in test_tls_handshake_done()
62 data->failed = qio_task_propagate_error(task, NULL); in test_tls_handshake_done()
79 "verify-peer", "yes", in test_tls_creds_create()
84 * and the test-crypto-tlscreds test already in test_tls_creds_create()
[all …]
|
| /openbmc/u-boot/drivers/net/phy/ |
| H A D | mv88e61xx.c | 1 // SPDX-License-Identifier: GPL-2.0+
43 #define PORT_MASK ((1 << PORT_COUNT) - 1)
228 val = bus->read(bus, smi_addr, MDIO_DEVAD_NONE, SMI_CMD_REG); in mv88e61xx_smi_wait()
233 } while (--timeout); in mv88e61xx_smi_wait()
236 return -ETIMEDOUT; in mv88e61xx_smi_wait()
243 * which on-chip register set you are reading/writing (the various PHYs, their
248 * single-chip addressing mode, where it responds to all SMI addresses, using
252 * non-zero address, it only responds to that SMI address and requires indirect
257 struct mv88e61xx_phy_priv *priv = phydev->priv; in mv88e61xx_reg_read()
258 struct mii_dev *mdio_bus = priv->mdio_bus; in mv88e61xx_reg_read()
[all …]
|