OpenBMC Distribution (mirror) https://git.radix-linux.su/BMC/tmp/openbmc.git/atom?h=2.12.0-dev 2021-12-08T06:49:44+00:00 2021-12-08T06:49:44+00:00 Lotus Xu xuxiaohan@bytedance.com 2021-12-08T06:21:07+00:00 urn:sha1:7bfedcf46b05c55266fb7bdd253ce81975dfa9d9 Tested: Test on qemu ipmi chassis status cmd work correct Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com> Change-Id: I60d20bf58c21b5c81d5fbad7649c1e2b43351392 2021-12-02T16:24:21+00:00 Alexander Filippov a.filippov@yadro.com 2021-12-02T16:16:20+00:00 urn:sha1:39d68d4071b8e9b61210e8bbe65d68a9662d0f34 `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 <a.filippov@yadro.com> 2021-11-04T13:28:28+00:00 Lei YU yulei.sh@bytedance.com 2021-09-08T07:21:51+00:00 urn:sha1:63beff091aac817713eedcd48fab1ff54136cbf8 With the upstream aspeed-uart-routing changes, the user space interface needs to be updated to use the new path. Tested: Verify the SOL is working fine on g220a. Signed-off-by: Lei YU <yulei.sh@bytedance.com> Change-Id: I4313d240b2778ef8070214eb19029b559588bcea 2021-11-04T13:28:28+00:00 Lei YU yulei.sh@bytedance.com 2021-11-03T05:16:23+00:00 urn:sha1:45ff79b865bea6f8ffc5f7a27b8c5181e87ff89b The aspeed-uart-routing patches are in openbmc linux tree now. Remove them from this layer. The remaining patch will be submitted to the openbmc linux tree as well and will be removed after it's merged. Signed-off-by: Lei YU <yulei.sh@bytedance.com> Change-Id: I5d9db3701fe7b2e92e4960155c9b3e24fefdaf23 2021-11-04T09:36:33+00:00 Patrick Williams patrick@stwcx.xyz 2021-11-03T15:35:37+00:00 urn:sha1:5a5f33c729e6b5869362172b63595422eb84a418 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 <patrick@stwcx.xyz> 2021-10-26T16:15:19+00:00 Patrick Williams patrick@stwcx.xyz 2021-10-22T20:30:00+00:00 urn:sha1:060ad3ff7fcc30aff78a9e504efee9d8fa0d4526 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 <patrick@stwcx.xyz> Change-Id: I20ca1fa8ff3cb01cac2d07d4ded84e0769e4514b 2021-10-26T16:14:46+00:00 Patrick Williams patrick@stwcx.xyz 2021-10-22T19:26:27+00:00 urn:sha1:ade3e145ead0beedad181394fcaa63856176bdee 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 <patrick@stwcx.xyz> Change-Id: Ifafb79e4e4c010e9476b9547cd4982f5b645060e 2021-10-25T03:26:42+00:00 Lei YU yulei.sh@bytedance.com 2021-10-25T03:26:42+00:00 urn:sha1:c06258c00235cb05d741309cb456e800cc6532d4 The node manager is maintained in https://github.com/Intel-BMC/node-manager and it is not buildable with latest OpenBMC. The OpenBMC guideline[1] and the repotest[2] does not accept pathces in machine layers, so the patches to node-manager are not accepted. Remove the recipe for now, otherwise the build fails. [1]: https://github.com/openbmc/docs/blob/master/meta-layer-guidelines.md [2]: https://github.com/openbmc/openbmc-build-scripts/blob/master/build-setup.sh#L141 Signed-off-by: Lei YU <yulei.sh@bytedance.com> Change-Id: I735f5b4d9b1cfa0ff4c0e47d349f99e847c0a7bd 2021-09-24T01:57:41+00:00 Lotus Xu xuxiaohan@bytedance.com 2021-09-22T10:25:57+00:00 urn:sha1:98f38d4c8d94db6fe6156e87bbe37b2c0cf64f4d Remove ipmb patch that is upstreamed Fix uart patch conflict Tested: Build ok Signed-off-by: Lotus Xu <xuxiaohan@bytedance.com> Change-Id: I3749aafb5957e1fda4d31ef44fb2b6b956baa94a 2021-09-16T12:54:14+00:00 Andrew Jeffery andrew@aj.id.au 2021-09-14T23:42:36+00:00 urn:sha1:605c37cb989a95c02633fcb93efb45102781b4bb 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 <andrew@aj.id.au> Signed-off-by: Patrick Williams <patrick@stwcx.xyz>