Lines Matching full:hpe

11 BMC needs a process to identify and handle HPE GXP baseboards that provide HW ID
33 HPE hardware uses different channels and data formats from the above, relying on
41 HPE platforms provide the following properties for baseboard VPD:
52 HPE platforms in Gen 10 and earlier provided VPD through a standard
54 no longer available on newer HPE systems.
56 For GXP-based Gen 11 HPE platforms, proprietary HPE-controlled bootblock
63 Early in the boot process, an HPE-proprietary bootblock is validated, then an
64 HPE-specific bootloader in the block fetches the VPD blob from the secure
66 predetermined location in RAM, where it is retrieved and parsed by HPE-specific
69 upstream as much 'HPE-critical' u-boot code as needed so that an HPE-specific
70 u-boot fork will not be needed to boot HPE hardware.
74 CPLD-based memory device. This value is unique to each model of HPE platform,
79 The HPE process described above relies on shared memory instead of u-boot env
80 variables because the HPE bootloader does not know that u-boot will run next,
100 identification of HPE baseboard hardware.
102 In the future, HPE's behind-the-scenes reliance on u-Boot for this process may
110 Entity-Manager to enable BMC detection and handling of HPE Gen 11 hardware (and
128 - At boot, a proprietary HPE bootblock is validated, then HPE GXP-bootloader
134   [open source, but HPE-specific process](https://github.com/HewlettPackard/gxp-uboot))
169 2. The critical identifier HPE wants to rely on for platform identification
175    potential for non-HPE platform to make easy use of it. Relying on 'model' as
177    outside of HPE-specific applications.
193    defacto HPE-specific code.
207 2. HPE component that retrieves VPD from HPE's secure element has no
210 ### Use an HPE-specific daemon instead of a generalized'[channel]-> D-Bus'<br/>daemon
215 2. Would only fire for HPE platforms
220 1. Doesn't save much effort compared to a generalized non-HPE-specific solution
312    HPe thinks are important [today] globbed into a new interface" interface"
351 Entity-Manager will also have configuration files added for HPE hardware that
364 validation) of the new D-Bus path can be validated on an HPE system by setting
365 an Entity-Manager config's probe to trigger on match with a known HPE-HW
370 At this time, HPE hardware requires forked (publicly available) OBMC components
371 to fully boot, so automated testing of HPE hardware against 'mainstream' OBMC