Home
last modified time | relevance | path

Searched refs:ME (Results 1 – 25 of 56) sorted by relevance

123

/openbmc/linux/Documentation/driver-api/mei/
H A Dhdcp.rst6 ME FW as a security engine provides the capability for setting up
10 ME FW prepares HDCP2.2 negotiation parameters, signs and encrypts them
14 Similarly, the HDCP2.2 sink's response is transferred to ME FW
18 upon request ME FW will configure the port as authenticated and supply
H A Dmei.rst6 The Intel Management Engine (Intel ME) is an isolated and protected computing
7 resource (Co-processor) residing inside certain Intel chipsets. The Intel ME
12 is the interface between the Host and Intel ME. This interface is exposed
15 a host application and the Intel ME features.
17 Each Intel ME feature, or Intel ME Client is addressed by a unique GUID and
27 An application maintains communication with an Intel ME feature while
30 The number of instances of an Intel ME feature that can be opened
31 at the same time depends on the Intel ME feature, but most of the
37 Because some of the Intel ME features can change the system
47 virtual channels with an Intel ME feature. Not all features support
H A Dmei-client-bus.rst4 Intel(R) Management Engine (ME) Client bus API
12 data to the many FW appliance found in Intel's ME from the user space.
13 However, for some of the ME functionalities it makes sense to leverage existing software
56 To actually register a driver on the ME Client bus one must call the :c:func:`mei_cl_add_driver`
79 As a theoretical example let's pretend the ME comes with a "contact" NFC IP.
/openbmc/linux/drivers/misc/mei/
H A DKconfig7 The Intel Management Engine (Intel ME) provides Manageability,
15 tristate "ME Enabled Intel Chipsets"
19 MEI support for ME Enabled Intel chipsets.
40 tristate "Intel Trusted Execution Environment with ME Interface"
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-class-mei23 The ME FW writes its status information into fw status
62 Description: Display the ME firmware version.
64 The version of the platform ME firmware is in format:
73 Description: Display the ME device state.
90 The ME FW writes Glitch Detection HW (TRC)
/openbmc/linux/drivers/misc/mei/hdcp/
H A DKconfig5 tristate "Intel HDCP2.2 services of ME Interface"
11 Enables the ME FW services required for HDCP2.2 support through
/openbmc/linux/drivers/misc/mei/pxp/
H A DKconfig6 tristate "Intel PXP services of ME Interface"
12 Enables the ME FW services required for PXP support through
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/openbox/files/
H A D0001-openbox-xdg-autostart-convert-to-python3.patch28 - print >>sys.stderr, "ERROR:", ME, "requires PyXDG to be installed"
31 + print("ERROR:", ME, "requires PyXDG to be installed", file=sys.stderr)
79 - print "Usage:", ME, "[OPTION]... [ENVIRONMENT]..."
102 + print("Usage:", ME, "[OPTION]... [ENVIRONMENT]...")
127 - print ME, VERSION
130 + print(ME, VERSION)
/openbmc/openbmc/poky/meta/recipes-core/systemd/systemd/
H A D0008-implment-systemd-sysv-install-for-OE.patch24 - echo "IMPLEMENT ME: enabling SysV init.d script $NAME"
30 - echo "IMPLEMENT ME: disabling SysV init.d script $NAME"
36 - echo "IMPLEMENT ME: checking SysV init.d script $NAME"
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/sdbus-c++/sdbus-c++-libsystemd/
H A D0008-implment-systemd-sysv-install-for-OE.patch24 - echo "IMPLEMENT ME: enabling SysV init.d script $NAME"
30 - echo "IMPLEMENT ME: disabling SysV init.d script $NAME"
36 - echo "IMPLEMENT ME: checking SysV init.d script $NAME"
/openbmc/intel-ipmi-oem/docs/
H A DIntel_IPMI_Platform_Events.md8 events originating from Intel Management Engine (ME) is used as a case-study.
18 - **ME** - Intel Management Engine, autonomous subsystem used for remote
37 extenstions to platform event data. One of these sources is Intel ME, which is
126 |0x2C (ME) |
131 . . . . |0x17 (ME Health)|
178 - Intel ME event parsing
197 in-place, while `ME` events are delegated to
307 'ME'.**
315 … "Description": "Indicates that Intel ME has reached certain threshold of flash write operations.",
356 5. [Intel ME External Interfaces Specification](https://www.intel.com/content/dam/www/public/us/en/…
/openbmc/qemu/docs/config/
H A Dmach-virt-serial.cfg13 # CHANGE ME before being able to use this configuration!
108 file = "/usr/share/AAVMF/AAVMF_CODE.fd" # CHANGE ME
115 file = "guest_VARS.fd" # CHANGE ME
214 file = "guest.qcow2" # CHANGE ME
225 file = "install.iso" # CHANGE ME
H A Dmach-virt-graphical.cfg12 # CHANGE ME before being able to use this configuration!
102 file = "/usr/share/AAVMF/AAVMF_CODE.fd" # CHANGE ME
109 file = "guest_VARS.fd" # CHANGE ME
208 file = "guest.qcow2" # CHANGE ME
219 file = "install.iso" # CHANGE ME
H A Dq35-virtio-graphical.cfg11 # CHANGE ME before being able to use this configuration!
159 file = "guest.qcow2" # CHANGE ME
170 file = "install.iso" # CHANGE ME
254 driver = "none" # CHANGE ME
H A Dq35-emulated.cfg11 # CHANGE ME before being able to use this configuration!
148 file = "guest.qcow2" # CHANGE ME
159 file = "install.iso" # CHANGE ME
294 driver = "none" # CHANGE ME
H A Dq35-virtio-serial.cfg12 # CHANGE ME before being able to use this configuration!
164 file = "guest.qcow2" # CHANGE ME
175 file = "install.iso" # CHANGE ME
/openbmc/linux/Documentation/driver-api/media/drivers/
H A Dtuners.rst55 F[IRMQ]12[1345]6{MF|ME|MP}
68 {MF|ME|MP}
70 ME: BG DK I LL (Multi Europe)
/openbmc/openbmc/meta-bytedance/meta-g220a/recipes-phosphor/datetime/me-time-sync/
H A Dme-time-sync.service2 Description=Sync time from ME
/openbmc/openbmc/meta-bytedance/meta-g220a/recipes-phosphor/datetime/
H A Dme-time-sync.bb1 SUMMARY = "ME time sync"
/openbmc/linux/drivers/misc/mei/gsc_proxy/
H A DKconfig5 tristate "Intel GSC Proxy services of ME Interface"
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-uefi-firmware_1.11.bb5 modules for BIOS, OptionROM, Intel ME and other formats too."
/openbmc/linux/sound/pci/aw2/
H A Dsaa7146.h46 #define ME (1UL << 11) macro
/openbmc/linux/arch/arm/mm/
H A Dcopypage-v6.c21 #error FIX ME
/openbmc/ipmbbridge/
H A DREADME.md64 type : This points to the ChannelType. It can be ME or ipmb channel.
/openbmc/linux/arch/arm/boot/dts/ti/omap/
H A Dam335x-moxa-uc-8100-me-t.dts12 model = "Moxa UC-8100-ME-T";

123