BMC/tmp/openbmc.git/meta-amd, branch honister

Remove BBLAYERS_NON_REMOVABLE variable

2021-12-02T16:24:21+00:00

`BBLAYERS_NON_REMOVABLE` is obsolete and no longer required. As it said by Yocto documentation it can be used by `Hob` https://www.yoctoproject.org/docs/1.5.2/ref-manual/ref-manual.html#var-BBLAYERS_NON_REMOVABLE that already removed since Yocto-2.1 https://www.yoctoproject.org/tools-resources/projects/hob Change-Id: Ibc2d8268a9d837a81e9cf6b0131dba8d0a030a3f Signed-off-by: Alexander Filippov

Partially revert "treewide: remove obmc-system-mgmt feature"

2021-11-04T09:36:33+00:00

The obmc-system-mgmt feature is currently used in the image to trigger inclusion of a virtual-provider which provides a number of packages many systems need. Partially revert the removal of this feature so that the outcome is: 1. The empty obmc-phosphor-sysd package is still removed. 2. By default the 'obmc-system-mgmt' feature is included, unless specifically exempted. 3. All EVB platforms remove the 'obmc-system-mgmt' feature since they have no system they are managing. This partially reverts commit 060ad3ff7fcc30aff78a9e504efee9d8fa0d4526. Tested: * Built `bletchley` and confirmed `packagegroup-fb-apps-system` and `entity-manager` are present. ``` entity-manager armv7ahf-vfpv4d16 0.1+git0+6bf41588ab-r0 packagegroup-fb-apps-system all 1.0-r1 ``` * Built `witherspoon` and confirmed `packagegroup-op-apps-system` and `pdbg` are present. ``` packagegroup-op-apps-system noarch 1.0 pdbg arm1176jzs 3.3 ``` * Ran `bitbake -p` on `evb-ast2600` to confirm the undefined `virtual-obmc-system-mgmt` is not being included in the image. Change-Id: I8b7804d5101cc84a2c57473b3f85672bf7767c67 Signed-off-by: Patrick Williams

treewide: remove obmc-system-mgmt feature

2021-10-26T16:15:19+00:00

Every machine layer treats 'system-management' as either part of a package-group or removes the feature. The sample implementation in meta-phosphor is a do-nothing shell script (and up until recently was a Python script). There appears to be no useful purpose to this feature as a stand-alone concept, so remove it. Signed-off-by: Patrick Williams Change-Id: I20ca1fa8ff3cb01cac2d07d4ded84e0769e4514b

treewide: clean up use of OBMC_MACHINE_FEATURES

2021-10-26T16:14:46+00:00

Modify the machine meta-layer configs to remove the use of the OBMC_MACHINE_FEATURES indirection and favor the Yocto MACHINE_FEATURES variable instead. Signed-off-by: Patrick Williams Change-Id: Ifafb79e4e4c010e9476b9547cd4982f5b645060e

treewide: fix comments for rpm/ipk

2021-09-16T19:23:05+00:00

Signed-off-by: Patrick Williams Change-Id: Ia05891430c6c97a89b7bc8ba4558ae496866bf7d

bitbake: Use IPK packaging for rootfs assembly

2021-09-16T12:54:14+00:00

bitbake offers a choice of DEB, RPM or IPK packaging. To a degree the choice is functionally arbitrary for image generation but control over the package format becomes important if we want to: 1. Include runtime package management functionality in the firmware image 2. Mess about with the packages on the build system With respect to 1 the IPK format and opkg (an ipk package manager) are designed for embedded systems[1] - by contrast to RPMs have heavier dependencies and a greater impact on the size and complexity of the firmware image. Regarding 2, the embedded nature and the need for opkg to work without much fuss leads to a lower configuration barrier by comparison to RPMs. With ipk it becomes possible to reuse the packages built during image preparation for core analysis without needing to generate an SDK: ``` $ export LD_LIBRARY_PATH=./tmp/work/x86_64-linux/opkg-native/*/recipe-sysroot-native/usr/lib $ MY_DEBUG_ROOT=tmp/rootfs-debug $ ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \ -f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/*/opkg.conf \ -o $MY_DEBUG_ROOT \ update $ fakeroot ./tmp/sysroots-components/x86_64/opkg-native/usr/bin/opkg \ -f ./tmp/work/p10bmc-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/opkg.conf \ -o $MY_DEBUG_ROOT \ install dbus-sensors dbus-sensors-dbg $ gdb-multiarch (gdb) set solib-absolute-prefix .../tmp/rootfs-debug (gdb) add-auto-load-safe-path .../tmp/rootfs-debug (gdb) file tmp/rootfs-debug/usr/bin/nvmesensor (gdb) core-file obmcdump_17_9597/core.nvmesensor.0.aae91b519d0e4e0e8bbe746e3f6cd25f.2779.9594000000 Core was generated by `/usr/bin/nvmesensor'. Program terminated with signal SIGABRT, Aborted. pthread_kill.c:45 45 pthread_kill.c: No such file or directory. (gdb) bt pthread_kill.c:45 ../sysdeps/posix/raise.c:26 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 /home/andrew/src/openbmc/openbmc/build/p10bmc/tmp/rootfs-debug/usr/lib/libstdc++.so.6 "xyz.openbmc_project.NVMeSensor", this=0x488f04) at /usr/include/sdbusplus/bus.hpp:234 ../../../../../../workspace/sources/dbus-sensors/src/NVMeSensorMain.cpp:159 (gdb) ``` This approach documented in the Poky Reference Manual: https://www.yoctoproject.org/docs/1.0/poky-ref-manual/poky-ref-manual.html#platdev-gdb-remotedebug-launch-gdb-inferiorbins Switch all machines to IPK to align the debugging experience with upstream's documentation and to facilitate efficient use of packaged software at runtime. [1] https://openwrt.org/docs/guide-user/additional-software/opkg Change-Id: I8ef526add2d7a6790de1b3eb3fb85cd39b864f23 Signed-off-by: Andrew Jeffery Signed-off-by: Patrick Williams

meta-amd: fix compilation errors with latest Yocto

2021-09-10T13:22:18+00:00

Make the following changes to fix compilation errors: - add honister to the LAYERSERIES_COMPAT variable, - increase CONF_VERSION to 2, - use new bitbake override syntax Signed-off-by: Konstantin Aladyshev Change-Id: I971f0f0f7110e0350994ced151ca429444885056

meta-ethanolx: Add driver for the FRU EEPROM

2021-09-10T13:22:07+00:00

AMD EthanolX CRB uses 24LC128 EEPROM as a device that is supposed to store FRU information. Add necessary Linux driver that adds support for this chip. Signed-off-by: Konstantin Aladyshev Change-Id: Iaf54bfd5bfbc3266d2a18861ee47339df78c777b

meta-ethanolx: Fix CPU fan names in IPMI YAML file

2021-08-30T13:29:08+00:00

The BMC on the AMD Ethanol CRB uses entity-manager for sensor configuration. Therefore IPMI configuration YAML file should use DBus paths to sensors based on the names from the entity-manager JSON files. Currently 'ethanolx-chassis.json' exports CPU fans on a DBus as "P0_Fan"/"P1_Fan". Use these names to correctly populate CPU fans to the IPMI. Signed-off-by: Konstantin Aladyshev Change-Id: I0425e42771e1bfb36ad067dfcad5a23e5f180d67

meta-ethanolx: Add support for Legacy/EFI selector

2021-08-30T13:28:51+00:00

AMD EthanolX CRB is a board with x86-64 CPU, which means it can support both EFI and Legacy boot. Add 'boot_type' PACKAGECONFIG option for the phosphor-settings-manager package to support EFI/Legacy selector in the BMC boot override feature. This setting is designed for the possibility of setting boot override as: - "PC compatible" boot (legacy) - Extensible Firmware Interface Boot (EFI) Change-Id: I173c5b439b929e80f3a106f5e7775862f889ee16 Signed-off-by: Konstantin Aladyshev