OpenBMC Distribution (mirror) https://git.radix-linux.su/BMC/tmp/openbmc.git/atom?h=master 2021-10-22T18:45:16+00:00 2021-10-22T18:45:16+00:00 Patrick Williams patrick@stwcx.xyz 2021-10-13T01:28:34+00:00 urn:sha1:721bc3efa961c3da6495669c00d121c4d8d3c3a9 This machine is unbuildable and has not been updated in the requisite 2 months per https://lore.kernel.org/openbmc/YRUW7cazmCjW8VpP@heinlein/, so it is being deleted. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I232a7a2d3e678a2396732d96e38f864704ba5cae 2021-09-16T19:23:05+00:00 Patrick Williams patrick@stwcx.xyz 2021-09-16T19:23:05+00:00 urn:sha1:b3b2aee683e98b7ac06dfa9807b37d5ae11bb9f6 Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Ia05891430c6c97a89b7bc8ba4558ae496866bf7d 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> 2021-08-24T11:39:30+00:00 Patrick Williams patrick@stwcx.xyz 2021-08-23T21:26:20+00:00 urn:sha1:ce1426257525128c9c8f17e91afc6a60d1cb6244 We've typically kept these LAYERSERIES_COMPAT to 2 releases: the current and the upcoming. Remove 'gatesgarth' is it is now 2 releases back. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I5e812a94fed1738898af75c0fdee81996a5bbf20 2021-06-07T06:22:06+00:00 William A. Kennington III wak@google.com 2021-05-27T22:36:31+00:00 urn:sha1:76f91bca10fbb88a5e376f4a338baa30778f9ec8 This is apparently not actually working anymore and is removed in the next poky update. Change-Id: Ia1c6a258d124a4a30a14fc42e8e0bba95e64faeb Signed-off-by: William A. Kennington III <wak@google.com> 2021-04-12T18:51:03+00:00 Patrick Williams patrick@stwcx.xyz 2021-02-19T23:13:35+00:00 urn:sha1:830ca604fe9896aafade07e93416ae058cc2e6ad Most openbmc machines use DISTRO="openbmc-phosphor" but Thor has a "alibaba-openbmc" distro config file. This config file has nothing except an inclusion of the phosphor one, so remove this useless indirection. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I9d4038c7bd58112fe9f2396c71f9bbd285b148bf 2021-04-06T13:22:18+00:00 Andrew Geissler geissonator@yahoo.com 2021-03-31T20:08:43+00:00 urn:sha1:5cbb9c9fe72ec00f03a62ac162bb8ca5f5037b03 Latest upstream yocto has moved on to the 3.3 hardknott release Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163 2021-03-22T13:59:05+00:00 Anton D. Kachalov gmouse@google.com 2021-03-17T11:35:07+00:00 urn:sha1:cde0f094f52420ffa1cb0a235c22dba43297c255 This layer provides libseccomp. Signed-off-by: Anton D. Kachalov <gmouse@google.com> Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f 2021-02-08T22:29:43+00:00 moyan_yyb moyan.yyb@alibaba-inc.com 2021-02-03T08:55:13+00:00 urn:sha1:111b57c119533e0fc87cb654daecaa36b233b9e4 Signed-off-by: yongbing yang <SnowYang@linux.alibaba.com> Change-Id: Ic0248e729ac47d692c059648fcf60b297de2ae3d