弥合差距：将 HPE Gen11 引入 OpenBMC 主线.pdf

1、Jean-Marie VerdunChristian WalterBridging the Gap:Bringing HPE Gen11 into the OpenBMC MainlineBridging the Gap:Bringing HPE Gen11 into the OpenBMC MainlineJean-Marie Verdun-HPEChristian Walter 9elementsOPEN PLATFORM FIRMWARESupport your own ASICDifferent speed between teams/community and needsProvid

2、e long tail support and enhance capabilitiesChallenges(9Elements and HPE)Gen11 HPE BMC ASIC(HPE)Single core ARM Cortex A9 basedSupported bus:i2c,SPI,eSPI,PCIe(gen2),USB(gadget)Additional features:AES,VGA,real time video encoders(proprietary format),SiROTKernel/U-boot upstream status(HPE)Drivers are

3、written to prove functional featuresMany drivers upstream into the kernel directly instead of the openbmc kernelUpstream occurred starting kernel 5.10 and ongoing support has been providedCrypto accelerators arent supportedVideo encoder is not supported,only the thumbnailUser space upstream(HPE)Init

4、ial tentative from openbmc 2.8Slow(very slow)process,mainly related between disconnect of code styling from HPE engineers and Open Source community expectationLong tail of upstream needs,but added features have been createdEnhancements(HPE/9elements)iSCSI bootCommon image between systemsSiROT functi

5、ons with full secure transfer of ownershipBeing totally out of syncHPEs openBMC was rather oldUpstream only contains partial support of Gen11 machinesSome modules were forked three years agoChanges to the Yocto SyntaxMajority of the conflicts come from syntax errors need manual review and validation

6、 of each and every oneFixed SPI Flash Layout in openBMC(+.dts changes)and many more build errorsDeveloper ExperienceGXP Bootblock BinariesDifferent Binaries based on the GXP SoC One generation can contain multiple(?)different GXP SoCsRather complicated process to find the right b