<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/tmp/openbmc.git/meta-ibm/meta-romulus, branch 2.13.0-dev</title>
<subtitle>OpenBMC Distribution (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/tmp/openbmc.git/atom?h=2.13.0-dev</id>
<link rel='self' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/atom?h=2.13.0-dev'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/'/>
<updated>2022-04-22T14:19:35+00:00</updated>
<entry>
<title>treewide: drop unused meta-security layer</title>
<updated>2022-04-22T14:19:35+00:00</updated>
<author>
<name>Brad Bishop</name>
<email>bradleyb@fuzziesquirrel.com</email>
</author>
<published>2022-04-22T14:19:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=6ad72ee99dd2398ef9e669ada3f525cfb1e99b43'/>
<id>urn:sha1:6ad72ee99dd2398ef9e669ada3f525cfb1e99b43</id>
<content type='text'>
This was added with cde0f094f for libseccomp, but shortly after that
upstream moved libseccomp from meta-security to core (241c7d2e6).  As
such, meta-security is no longer used or required.

Signed-off-by: Brad Bishop &lt;bradleyb@fuzziesquirrel.com&gt;
Change-Id: I371e54b11f6336720dfc6edf0ef733d22b7fb4f2
</content>
</entry>
<entry>
<title>treewide: Update BB_DISKMON_DIRS use</title>
<updated>2022-04-12T16:58:47+00:00</updated>
<author>
<name>George Liu</name>
<email>liuxiwei@inspur.com</email>
</author>
<published>2022-04-12T06:01:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=b6bf8da1a58541fef58862e9c783d9bdad0d5c83'/>
<id>urn:sha1:b6bf8da1a58541fef58862e9c783d9bdad0d5c83</id>
<content type='text'>
Per [1][2], Yocto is starting to deprecate ABORT and has replaced
the "ABORT" action in BB_DISKMON_DIRS entries with "HALT".

1. https://wiki.yoctoproject.org/wiki/Inclusive_language
2. https://git.yoctoproject.org/poky/commit/?id=4f77505d94a8f6260933f457e9848d1d2fa98ce5

Tested:
Built obmc-phosphor-image successfully and eliminate the following
warnings:

```
WARNING: The BB_DISKMON_DIRS "ABORT" action has been renamed to
"HALT", update configuration
```

Signed-off-by: George Liu &lt;liuxiwei@inspur.com&gt;
Change-Id: If57d0ded9fac41e23b31b01e2a0e309ac7388148
</content>
</entry>
<entry>
<title>Move Palmetto and Romulus from webui to webvue</title>
<updated>2022-03-21T18:48:03+00:00</updated>
<author>
<name>Abhishek Patel</name>
<email>Abhishek.Patel@ibm.com</email>
</author>
<published>2021-12-02T14:59:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=f0724165973eba995f271f077369502ec2b5c356'/>
<id>urn:sha1:f0724165973eba995f271f077369502ec2b5c356</id>
<content type='text'>
Palmetto and Romulus were using phosphor-webui. phosphor-webui built on
AngularJS, and AngularJS goes End of Life December 31, 2021.
So Move Plametto and Romulus to use webui-vue.
webui-vue is a modern replacement for phoshor-webui. Weui-vue is built
on vue.js, uses Redfish, and has additional features like
 - Ability to easily theme to meet brand guidelines
 - Accessibility
 - Full Redfish
 - Improved user experience based on user feedback
 - Language translation-ready
 - Modern front-end framework with an active community and future
   development roadmap

Tested: manually tested on Palmetto and Romulus system. Able to log in
        into the system using the latest webui-vue. Able to retrieve
        dump log and another log, all basic functionality is working.

Signed-off-by: Abhishek Patel &lt;Abhishek.Patel@ibm.com&gt;
Change-Id: I883a84552383f3d7f94d9227a11fc7410bc43ec5
</content>
</entry>
<entry>
<title>treewide: support yocto kirkstone release</title>
<updated>2022-02-25T21:29:44+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2022-02-25T21:28:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=757831f38b48e057618031bd4b16bdac0d7ac778'/>
<id>urn:sha1:757831f38b48e057618031bd4b16bdac0d7ac778</id>
<content type='text'>
* Deprecate N-1 release (hardknott).
* Enable N+1 release (kirkstone).

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I39e027e02dab64b4390b46ffbd9c299c858f403e
</content>
</entry>
<entry>
<title>meta-ibm: romulus: Fix QA warnings</title>
<updated>2022-02-18T21:35:33+00:00</updated>
<author>
<name>Peter Foley</name>
<email>pefoley@google.com</email>
</author>
<published>2022-02-09T15:29:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=f0e9a31b089275a4e27e7ac65cb35a9607ede30e'/>
<id>urn:sha1:f0e9a31b089275a4e27e7ac65cb35a9607ede30e</id>
<content type='text'>
e.g.
WARNING: /home/peter/openbmc/meta-ibm/meta-romulus/recipes-phosphor/occ/romulus-occ-control-config-native.bb: QA Issue: romulus-occ-control-config-native: native/nativesdk class is not inherited last, this can result in unexpected behaviour. Classes inherited after native/nativesdk: openpower-occ-control.bbclass [native-last]
WARNING: /home/peter/openbmc/meta-ibm/meta-romulus/recipes-phosphor/logging/romulus-phosphor-logging-callouts-native.bb: QA Issue: romulus-phosphor-logging-callouts-native: native/nativesdk class is not inherited last, this can result in unexpected behaviour. Classes inherited after native/nativesdk: phosphor-logging.bbclass [native-last]

Signed-off-by: Peter Foley &lt;pefoley@google.com&gt;
Change-Id: I31be11e264e1701215d2eadd28dc2249153a5d61
</content>
</entry>
<entry>
<title>treewide: fix up github SRC_URIs</title>
<updated>2022-01-25T16:37:00+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2022-01-24T21:55:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=bb99d22ecef61f3af21290b1e1ead3083f25d20f'/>
<id>urn:sha1:bb99d22ecef61f3af21290b1e1ead3083f25d20f</id>
<content type='text'>
Per [1], Yocto is going to start requiring both branch names and
`protocol=https` in GitHub SRC_URI variables.  Ran the upstream tool to
automatically fix our URIs.

1. https://git.yoctoproject.org/poky/tree/documentation/migration-guides/migration-3.5.rst#n10

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I5f9619f7ff707050b469ae74c8aa16846568c5e4
</content>
</entry>
<entry>
<title>u-boot: Specify u-boot package for AST2500 machines</title>
<updated>2022-01-18T12:11:43+00:00</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2022-01-17T10:34:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=a4c5b7f99891bd08d5c11b88f7abbc57b2ab8ea6'/>
<id>urn:sha1:a4c5b7f99891bd08d5c11b88f7abbc57b2ab8ea6</id>
<content type='text'>
This sets u-boot to the package containing the v2016.07-aspeed-openbmc
branch. This ensures there will be no change if the default changes in
the future.

Change-Id: Iea12e1691dbdda34a3f95d6d0862add0b15bcf37
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>Remove BBLAYERS_NON_REMOVABLE variable</title>
<updated>2021-12-02T16:24:21+00:00</updated>
<author>
<name>Alexander Filippov</name>
<email>a.filippov@yadro.com</email>
</author>
<published>2021-12-02T16:16:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=39d68d4071b8e9b61210e8bbe65d68a9662d0f34'/>
<id>urn:sha1:39d68d4071b8e9b61210e8bbe65d68a9662d0f34</id>
<content type='text'>
`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 &lt;a.filippov@yadro.com&gt;
</content>
</entry>
<entry>
<title>treewide: fix comments for rpm/ipk</title>
<updated>2021-09-16T19:23:05+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-09-16T19:23:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=b3b2aee683e98b7ac06dfa9807b37d5ae11bb9f6'/>
<id>urn:sha1:b3b2aee683e98b7ac06dfa9807b37d5ae11bb9f6</id>
<content type='text'>
Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: Ia05891430c6c97a89b7bc8ba4558ae496866bf7d
</content>
</entry>
<entry>
<title>bitbake: Use IPK packaging for rootfs assembly</title>
<updated>2021-09-16T12:54:14+00:00</updated>
<author>
<name>Andrew Jeffery</name>
<email>andrew@aj.id.au</email>
</author>
<published>2021-09-14T23:42:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=605c37cb989a95c02633fcb93efb45102781b4bb'/>
<id>urn:sha1:605c37cb989a95c02633fcb93efb45102781b4bb</id>
<content type='text'>
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 &lt;andrew@aj.id.au&gt;
Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
</content>
</entry>
</feed>
