| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0009-FF-A-v15-arm_ffa-efi-introduce-FF-A-MM-communication.patch | 4 Subject: [PATCH] FF-A v15: arm_ffa: efi: introduce FF-A MM communication
6 Add MM communication support using FF-A transport
9 EFI MM communication protocol. MM partitions such as StandAlonneMM
16 and copied from the communication buffer to the MM shared buffer.
24 The response data is copied back to the communication buffer and
27 MM communication protocol supports FF-A 64-bit direct messaging.
65 * communication channel with the Standalone MM (Management Mode)
108 + int "Memory size of the shared MM communication buffer"
113 + buffer used for communication between the MM feature in U-Boot and
117 + It is assumed that the MM SP knows the size of the shared MM communication buffer.
[all …]
|
| H A D | 0010-FF-A-v15-arm_ffa-efi-corstone1000-enable-MM-communic.patch | 4 Subject: [PATCH] FF-A v15: arm_ffa: efi: corstone1000: enable MM communication
6 turn on EFI MM communication
8 On corstone1000 platform MM communication between u-boot
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/MCTP/ |
| H A D | Endpoint.interface.yaml | 2 Describe an MCTP endpoint. It is an MCTP communication terminus. An MCTP
22 a particular MCTP endpoint within a system for MCTP communication and
24 that comprise an MCTP communication network within a system. MCTP EIDs
34 communication payload in an MCTP message. The well defined message
|
| /openbmc/u-boot/drivers/mailbox/ |
| H A D | Kconfig | 10 the basis of a variety of inter-process/inter-CPU communication
32 Texas Instruments. Secure proxy is a communication entity mainly
33 used for communication between multiple processors with the SoC.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/libiec61850/ |
| H A D | libiec61850_1.5.3.bb | 3 communication systems in Substation Automation Systems \
5 (DER). It is seen as one of the communication standards \
9 61850-9-2/Sampled Values communication protocols \
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | VSL-1.0 | 5 Open Communication Application Library" except for those portions
24 3. The names "VOCAL", "Vovida Open Communication Application Library",
25 and "Vovida Open Communication Application Library (VOCAL)" must
|
| H A D | EUPL-1.2 | 31 — ‘Distribution’ or ‘Communication’:any act of selling, giving, lending, renting, distributing, com…
53 3.Communication of the Source Code
75 Distribution or Communication will be done under the terms of this Licence or of a later version of…
81 the Work and another work licensed under a Compatible Licence, this Distribution or Communication c…
131 or Communication by You of the Work or copies thereof.
134 In case of any Distribution or Communication of the Work by means of electronic communication by Yo…
|
| H A D | EUPL-1.0 | 35 Software under the terms of the Licence. − Distribution and/or Communication: any act of sell…
57 3. Communication of the Source Code
76 Communication will be done under the terms of this Licence. The Licensee (becoming
81 Compatible Licence, this Distribution and/or Communication can be done under the terms of
137 the creation by You of a Derivative Work or the Distribution and/or Communication by You
140 In case of any Distribution and/or Communication of the Work by means of electronic
141 communication by You (for example, by offering to download the Work from a remote
|
| H A D | EUPL-1.1 | 36 - Distribution and/or Communication: any act of selling, giving, lending, renting,
61 3. Communication of the Source Code
85 and/or Communication will be done under the terms of this Licence or of a later
92 licensed under a Compatible Licence, this Distribution and/or Communication can be
153 Communication by You of the Work or copies thereof.
155 In case of any Distribution and/or Communication of the Work by means of electronic
156 communication by You (for example, by offering to download the Work from a
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | ComponentIntegrity.v1_3_1.json | 83 "description": "Information about communication between two components.",
84 …"longDescription": "This object shall contain information about communication between two componen…
101 … "description": "The active sessions or communication channels between two components.",
112 … or communication channels between two components. The active sessions or communication channels …
168 …ntIntegrityType` property. If the service has not established secure communication with the devic…
492 "description": "Information about communication between two components.",
493 …"longDescription": "This object shall contain information about communication between two componen…
510 … "description": "The active sessions or communication channels between two components.",
521 … or communication channels between two components. The active sessions or communication channels …
601 … "description": "Information about communication between the SPDM Requester and SPDM Responder.",
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | ComponentIntegrity.v1_3_1.json | 83 "description": "Information about communication between two components.",
84 …"longDescription": "This object shall contain information about communication between two componen…
101 … "description": "The active sessions or communication channels between two components.",
112 … or communication channels between two components. The active sessions or communication channels …
168 …ntIntegrityType` property. If the service has not established secure communication with the devic…
492 "description": "Information about communication between two components.",
493 …"longDescription": "This object shall contain information about communication between two componen…
510 … "description": "The active sessions or communication channels between two components.",
521 … or communication channels between two components. The active sessions or communication channels …
601 … "description": "Information about communication between the SPDM Requester and SPDM Responder.",
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Condition/ |
| H A D | HostFirmware.interface.yaml | 24 Host firmware is not responsive to communication
27 Host firmware is running and responsive to communication
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-filter/libnfnetlink/ |
| H A D | libnfnetlink_1.0.2.bb | 1 SUMMARY = "Low-level library for netfilter related kernel/userspace communication"
3 kernel/userspace communication. It provides a generic messaging \
|
| /openbmc/openbmc/meta-facebook/meta-minerva/recipes-phosphor/images/ |
| H A D | fb-minerva-phosphor-image.inc | 40 # Enable mdio-tools for communication with the PHY chip
50 # Enable mbpoll for communication with the smart valve by modbus command
|
| /openbmc/u-boot/arch/arm/mach-tegra/ |
| H A D | Kconfig | 18 IVC (Inter-VM Communication) protocol is a Tegra-specific IPC
19 (Inter Processor Communication) framework. Within the context of
20 U-Boot, it is typically used for communication between the main CPU
|
| /openbmc/u-boot/arch/powerpc/include/asm/ |
| H A D | immap_8xx.h | 6 * and the dual port ram for the Communication Processor Module.
214 /* Communication Processor Module Interrupt Controller.
247 /* Communication Processor Module Timers
275 /* Finally, the Communication Processor stuff.....
277 typedef struct scc { /* Serial communication channels */
366 /* Serial Communication Channels.
465 cpm8xx_t im_cpm; /* Communication processor */
|
| /openbmc/qemu/docs/system/i386/ |
| H A D | nitro-enclave.rst | 9 on Firecracker microvm with a vhost-vsock device for communication with the
21 must be run alongside nitro-enclave for the vsock communication to work.
59 applications' vsock communication works. For example, the nitro-enclave VM's init
65 VM for successful communication with the enclave VM.
|
| /openbmc/google-misc/subprojects/nemora-postd/ |
| H A D | nemorad.cpp | 63 "communication, i.e., POST streaming.") in main()
69 "communication, i.e., POST streaming.") in main()
75 "Network interface for TCP communication. Ex: eth0") in main()
|
| /openbmc/u-boot/arch/arm/include/asm/arch-tegra/ |
| H A D | ivc.h | 12 * Tegra IVC is a communication protocol that transfers fixed-size frames
14 * Communication is via a statically sized and allocated buffer in shared
146 * @return 0 if the channel is ready for communication, or -EAGAIN if a
155 * is used for communication. The channel will be ready for use when a
|
| /openbmc/u-boot/arch/powerpc/cpu/mpc85xx/ |
| H A D | commproc.c | 9 * 8220 Communication Processor Module.
15 * In addition to the individual control of the communication
17 * communication processor.
20 * space. The allocator for that is here. When the communication
|
| /openbmc/u-boot/doc/device-tree-bindings/mailbox/ |
| H A D | nvidia,tegra186-hsp.txt | 5 interprocessor communication. So the interprocessor communication (IPC)
|
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team.md | 37 communication vehicle between the person who reported the problem and the
38 security response team, and the initial communication between the security
|
| /openbmc/u-boot/drivers/sysreset/ |
| H A D | sysreset-ti-sci.c | 17 * @sci: TI SCI handle used for communication with system controller
32 /* Store handle for communication with the system controller */ in ti_sci_sysreset_probe()
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | keystone-k2g-ice.dts | 3 * Device Tree Source for K2G Industrial Communication Engine EVM
13 model = "Texas Instruments K2G Industrial Communication EVM";
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | pel_values.cpp | 54 {0x41, "io_adapter_comm", "I/O Adapter Communication"},
94 "Hypervisor lost communication with service processor"},
96 "Service processor lost communication with Hypervisor"},
97 {0x7C, "surv_sp_lost_hmc", "Service processor lost communication with HMC"},
99 "HMC lost communication with logical partition"},
100 {0x7E, "surv_hmc_lost_bpa", "HMC lost communication with BPA"},
101 {0x7F, "surv_hmc_lost_hmc", "HMC lost communication with another HMC"},
|