| /openbmc/bmcweb/redfish-core/include/ |
| H A D | error_messages.hpp | 31 * @brief Formats Success message into JSON
41 * @brief Formats GeneralError message into JSON
53 * @brief Formats Created message into JSON
63 * @brief Formats NoOperation message into JSON
74 * @brief Formats PropertyDuplicate message into JSON
85 * @brief Formats PropertyUnknown message into JSON
97 * @brief Formats PropertyValueTypeError message into JSON
112 * @brief Formats PropertyValueFormatError message into JSON
127 * @brief Formats PropertyValueNotInList message into JSON
142 * @brief Formats PropertyValueOutOfRange message into JSON
[all …]
|
| /openbmc/bmcweb/redfish-core/src/ |
| H A D | resource_messages.cpp | 54 * @brief Formats ResourceCreated message into JSON
67 * @brief Formats ResourceRemoved message into JSON
80 * @brief Formats ResourceErrorsDetected message into JSON
95 * @brief Formats ResourceErrorsCorrected message into JSON
110 * @brief Formats ResourceErrorThresholdExceeded message into JSON
126 * @brief Formats ResourceErrorThresholdCleared message into JSON
142 * @brief Formats ResourceWarningThresholdExceeded message into JSON
158 * @brief Formats ResourceWarningThresholdCleared message into JSON
174 * @brief Formats ResourceStatusChangedOK message into JSON
189 * @brief Formats ResourceStatusChangedWarning message into JSON
[all …]
|
| H A D | update_messages.cpp | 53 * @brief Formats TargetDetermined message into JSON
67 * @brief Formats AllTargetsDetermined message into JSON
79 * @brief Formats NoTargetsDetermined message into JSON
92 * @brief Formats UpdateInProgress message into JSON
104 * @brief Formats TransferringToComponent message into JSON
118 * @brief Formats VerifyingAtComponent message into JSON
132 * @brief Formats InstallingOnComponent message into JSON
146 * @brief Formats ApplyingOnComponent message into JSON
160 * @brief Formats TransferFailed message into JSON
174 * @brief Formats VerificationFailed message into JSON
[all …]
|
| H A D | error_messages.cpp | 59 * @brief Formats Success message into JSON
76 * @brief Formats GeneralError message into JSON
94 * @brief Formats Created message into JSON
112 * @brief Formats NoOperation message into JSON
130 * @brief Formats PropertyDuplicate message into JSON
149 * @brief Formats PropertyUnknown message into JSON
168 * @brief Formats PropertyValueTypeError message into JSON
191 * @brief Formats PropertyValueFormatError message into JSON
214 * @brief Formats PropertyValueNotInList message into JSON
237 * @brief Formats PropertyValueOutOfRange message into JSON
[all …]
|
| H A D | task_messages.cpp | 54 * @brief Formats TaskStarted message into JSON
67 * @brief Formats TaskCompletedOK message into JSON
80 * @brief Formats TaskCompletedWarning message into JSON
93 * @brief Formats TaskAborted message into JSON
106 * @brief Formats TaskCancelled message into JSON
119 * @brief Formats TaskRemoved message into JSON
132 * @brief Formats TaskPaused message into JSON
145 * @brief Formats TaskResumed message into JSON
158 * @brief Formats TaskProgressChanged message into JSON
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libimport/ |
| H A D | libimport-into-perl_1.002004.bb | 1 SUMMARY = "Import::Into - import packages into other packages"
10 \"Import::Into\" provides global methods to make this painless."
14 HOMEPAGE = "https://metacpan.org/pod/Import::Into"
19 SRC_URI = "${CPAN_MIRROR}/authors/id/E/ET/ETHER/Import-Into-${PV}.tar.gz"
22 S = "${WORKDIR}/Import-Into-${PV}"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/fltk/fltk/ |
| H A D | fltk-native-link-libdl.patch | 15 0c1c3a771e dlfcn: Move dlopen into libc
16 add8d7ea01 dlfcn: Move dlvsym into libc
17 6dfc0207eb dlfcn: Move dlinfo into libc
18 492560a32e dlfcn: Move dladdr1 into libc
19 6a1ed32789 dlfcn: Move dlmopen into libc
20 77f876c0e3 dlfcn: Move dlsym into libc
21 602252b553 dlfcn: Move dladdr into libc
22 d8cce17d2a dlfcn: Move dlclose into libc
|
| /openbmc/qemu/docs/ |
| H A D | pcie_pci_bridge.txt | 16 can be hot-plugged into appropriate root port (requires additional actions,
18 and supports devices hot-plug into the bridge itself
21 Hot-plug of legacy PCI devices into the bridge
89 - 2 PCIE-PCI bridges plugged into 2 different root ports;
90 - e1000 plugged into the first bridge.
92 - PCIE-PCI bridge, plugged into QEMU generic root port;
93 - 2 e1000 cards, one plugged into the cold-plugged PCIE-PCI bridge,
94 another plugged into the hot-plugged bridge.
98 The PCIE-PCI bridge can be hot-plugged only into pcie-root-port that
102 Windows 7 and older versions don't support hot-plug devices into the PCIE-PCI bridge.
[all …]
|
| H A D | pcie.txt | 26 and allows any PCI/PCI Express device to be plugged into any
28 Plugging a PCI device into a PCI Express slot might not always work and
30 Plugging a PCI Express device into a PCI slot will hide the Extended
34 PCI Express devices should be plugged only into PCI Express Root Ports and
67 2.1.1 To plug a device into pcie.0 as a Root Complex Integrated Endpoint use:
86 Prefer grouping PCI Express Root Ports into multi-function devices
92 Plug only PCI Express devices into PCI Express Ports.
114 2.2.1 Plugging a PCI Express device into a PCI Express Root Port:
121 2.2.3 Plugging a PCI Express device into a Switch:
135 Legacy PCI devices can be plugged into pcie.0 as Integrated Endpoints,
[all …]
|
| /openbmc/qemu/target/loongarch/ |
| H A D | trace-events | 5 kvm_failed_put_regs_core(const char *msg) "Failed to put core regs into KVM: %s"
7 kvm_failed_put_fpu(const char *msg) "Failed to put fpu into KVM: %s"
9 kvm_failed_put_mpstate(const char *msg) "Failed to put mp_state into KVM: %s"
11 kvm_failed_put_counter(const char *msg) "Failed to put counter into KVM: %s"
13 kvm_failed_put_cpucfg(const char *msg) "Failed to put cpucfg into KVM: %s"
|
| /openbmc/qemu/rust/qemu-api/src/ |
| H A D | errno.rs | 8 //! into an [`io::Result`] and back.
12 /// An `errno` value that can be converted into an [`io::Error`]
18 // into io::Error by hand. This is the same mapping that the
81 io::Error::from_raw_os_error(errno.into()) in from()
86 let error_kind: ErrorKind = value.into(); in from()
87 error_kind.into() in from()
98 value.kind().into() in from()
107 /// A signed type that can be converted into an
118 /// converted into "positive success/negative `errno`" convention.
173 /// Convert an integer value into a [`io::Result`].
[all …]
|
| /openbmc/openbmc/poky/bitbake/lib/bs4/ |
| H A D | css.py | 84 :param flags: Flags to be passed into Soup Sieve's
87 :param kwargs: Keyword arguments to be passed into SoupSieve's
112 :param flags: Flags to be passed into Soup Sieve's
115 :param kwargs: Keyword arguments to be passed into SoupSieve's
142 :param flags: Flags to be passed into Soup Sieve's
145 :param kwargs: Keyword arguments to be passed into SoupSieve's
179 :param flags: Flags to be passed into Soup Sieve's
182 :param kwargs: Keyword arguments to be passed into SoupSieve's
206 :param flags: Flags to be passed into Soup Sieve's
209 :param kwargs: Keyword arguments to be passed into SoupSieve's
[all …]
|
| /openbmc/openbmc/meta-raspberrypi/classes/ |
| H A D | sdcard_image-rpi.bbclass | 65 # Additional files and/or directories to be copied into the vfat partition from the IMAGE_ROOTFS.
101 …AME}/* ::/ || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${BOOTFILES_DIR_NAME}/* into boot.img"
103 …${ARMSTUB} ::/ || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/armstubs/${ARMSTUB} into boot.img"
119 … ::${DEST_FILENAME} || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${DEPLOY_FILE} into boot.img"
123 … ::${SDIMG_KERNELIMAGE} || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/u-boot.bin into boot.img"
124 …MAGE}/boot.scr ::boot.scr || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/boot.scr into boot.img"
126 …mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${INITRAMFS_LINK_NAME}.bin into boot.img"
128 …NEL_IMAGETYPE} || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE} into boot.img"
132 …mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${INITRAMFS_LINK_NAME}.bin into boot.img"
134 …G_KERNELIMAGE} || bbfatal "mcopy cannot copy ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE} into boot.img"
[all …]
|
| /openbmc/u-boot/include/ |
| H A D | bouncebuf.h | 15 * The source buffer is copied into the bounce buffer (if unaligned, otherwise
22 * GEN_BB_WRITE -- Data are written into the buffer eg. by DMA hardware.
25 * copied into the destination buffer (if unaligned, otherwise destination
30 * GEN_BB_RW -- Data are read and written into the buffer eg. by DMA hardware.
31 * The source buffer is copied into the bounce buffer (if unaligned, otherwise
34 * into the destination buffer (if unaligned, otherwise destination buffer is
|
| H A D | fs_loader.h | 41 * request_firmware_into_buf - Load firmware into a previously allocated buffer.
44 * @buf: Address of buffer to load firmware into.
46 * @offset: Offset of a file for start reading into buffer.
48 * The firmware is loaded directly into the buffer pointed to by @buf.
|
| H A D | vsprintf.h | 99 * @param buf The buffer to place the result into
104 * into @buf.
114 * @param buf The buffer to place the result into
117 * @return the number of characters which have been written into
130 * @param buf The buffer to place the result into
147 * @param buf The buffer to place the result into
152 * The return value is the number of characters written into @buf not including
163 * @param buf The buffer to place the result into
188 * @param buf The buffer to place the result into
192 * @return the number of characters which have been written into
|
| /openbmc/u-boot/doc/ |
| H A D | README.falcon | 14 U-Boot is split into two parts: the SPL (Secondary Program Loader) and U-Boot
19 copies U-Boot image into the memory.
28 With Falcon Mode, this snapshot can be saved into persistent storage and SPL is
33 1. Boot the board into U-Boot.
34 After loading the desired legacy-format kernel image into memory (and DT as
39 2. Save the prepared snapshot into persistent media.
40 The address where to save it must be configured into board configuration
43 3. Boot the board into Falcon Mode. SPL will load the kernel and copy
116 or prepared FDT) from temporary storage in RAM into persistant storage
185 The parameters generated with this step can be saved into NAND at the offset
[all …]
|
| /openbmc/u-boot/arch/arm/cpu/armv7/ |
| H A D | cache_v7_asm.S | 28 mov r3, r0, lsr #23 @ move LoC into position
52 ARM( orr r11, r10, r4, lsl r5 ) @ factor way and cache number into r11
54 THUMB( orr r11, r10, r6 ) @ factor way and cache number into r11
55 ARM( orr r11, r11, r9, lsl r2 ) @ factor index number into r11
57 THUMB( orr r11, r11, r6 ) @ factor index number into r11
99 mov r3, r0, lsr #23 @ move LoC into position
122 ARM( orr r11, r10, r4, lsl r5 ) @ factor way and cache number into r11
124 THUMB( orr r11, r10, r6 ) @ factor way and cache number into r11
125 ARM( orr r11, r11, r9, lsl r2 ) @ factor index number into r11
127 THUMB( orr r11, r11, r6 ) @ factor index number into r11
|
| /openbmc/hiomapd/vpnor/ |
| H A D | README.md | 33 6. Access ranges that are valid may map into a backing file associated with the
35 7. A read of a valid access range that maps into the backing file will render
37 8. A read of a valid access range that does not map into the backing file will
40 10. A write to a valid access range that maps into the backing file will update
42 11. A write to a valid access range that does not map into the backing file will
|
| /openbmc/u-boot/board/wandboard/ |
| H A D | README | 20 Flashing U-Boot into the SD card
24 flashed into the SD card;
30 - Flash the u-boot.img image into the SD card:
34 - Insert the SD card into the slot located in the bottom of the board (same side
|
| /openbmc/libpldm/src/ |
| H A D | msgbuf.h | 24 * `pldm_msgbuf_ro` is used by decode APIs to extract payloads into PLDM
128 * Extract the field at the msgbuf cursor into the lvalue named by dst.
131 * @param dst The lvalue into which the field at the msgbuf cursor should be
147 * Extract the field at the msgbuf cursor into the object pointed-to by dst.
150 * @param dst The pointer to the object into which the field at the msgbuf
176 * Insert an array of data into the msgbuf instance
178 * @param ctx - The msgbuf instance into which the array of data should be
181 * @param src - The array object from which elements should be inserted into
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | trusted-services.md | 10 These files are automatically included into optee-os image accordingly to defined MACHINE_FEATURES.
14 To include TS SPs into optee-os image you need to add into MACHINE_FEATURES
32 …is required. If your platform doesn't include it already you can add `arm-ffa` into MACHINE_FEATUR…
53 Optionally for testing purposes you can add `packagegroup-ts-tests` into your image. It includes
59 See `ci/trusted-services.yml` for an example how to include them into an image.
71 | SMMGW_INTERNAL_CRYPTO | Bool | Use MbedTLS build into SmmGW for authentication related crypto ope…
|
| /openbmc/qemu/docs/devel/ |
| H A D | s390-dasd-ipl.rst | 15 2. Execute the Read IPL ccw at ``0x00``, thereby reading IPL1 data into ``0x00``.
18 IPL ccw it read the 24-bytes of IPL1 to be read into memory starting at
21 the original READ IPL ccw. The read ccw will read the IPL2 data into memory
34 the real operating system is loaded into memory and we are ready to hand
39 NOTE: The IPL2 channel program might read data into memory
48 The psw that was loaded into memory location ``0x0`` as part of the ipl process
71 1. Place a "Read IPL" ccw into memory location ``0x0`` with chaining bit on.
104 1. Place "Read IPL" ccw into memory location ``0x0``, but turn off chaining bit.
119 Now IPL2 is loaded into memory somewhere, and we know the address.
|
| /openbmc/openbmc/meta-arm/ci/ |
| H A D | qemuarm64-secureboot-ts.yml | 11 …# Include TS Crypto, TS Protected Storage, and TS Internal Trusted Storage and SPs into optee-os i…
14 # Include TS demo/test tools into image
16 # Include TS PSA Arch tests into image
|
| /openbmc/phosphor-mboxd/vpnor/ |
| H A D | README.md | 37 6. Access ranges that are valid may map into a backing file associated with
39 7. A read of a valid access range that maps into the backing file will render
41 8. A read of a valid access range that does not map into the backing file will
44 10. A write to a valid access range that maps into the backing file will update
46 11. A write to a valid access range that does not map into the backing file
|