<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/tmp/openbmc.git/meta-evb, branch 2.12.0-dev</title>
<subtitle>OpenBMC Distribution (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/tmp/openbmc.git/atom?h=2.12.0-dev</id>
<link rel='self' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/atom?h=2.12.0-dev'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/'/>
<updated>2021-12-02T16:24:21+00:00</updated>
<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>Partially revert "treewide: remove obmc-system-mgmt feature"</title>
<updated>2021-11-04T09:36:33+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-11-03T15:35:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=5a5f33c729e6b5869362172b63595422eb84a418'/>
<id>urn:sha1:5a5f33c729e6b5869362172b63595422eb84a418</id>
<content type='text'>
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 &lt;patrick@stwcx.xyz&gt;
</content>
</entry>
<entry>
<title>meta-evb-enclustra: remove unusable evb-zx3-pm3 machine</title>
<updated>2021-10-22T18:44:51+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-10-13T01:28:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=19fcaae0cd78ad73b85d2c213d194be70ac77d36'/>
<id>urn:sha1:19fcaae0cd78ad73b85d2c213d194be70ac77d36</id>
<content type='text'>
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 &lt;patrick@stwcx.xyz&gt;
Change-Id: Ifd83af863ed6211fbaa167a9862ef426c2120f09
</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>
<entry>
<title>treewide: remove gategarth from layer-support</title>
<updated>2021-08-24T11:39:30+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-08-23T21:26:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=ce1426257525128c9c8f17e91afc6a60d1cb6244'/>
<id>urn:sha1:ce1426257525128c9c8f17e91afc6a60d1cb6244</id>
<content type='text'>
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 &lt;patrick@stwcx.xyz&gt;
Change-Id: I5e812a94fed1738898af75c0fdee81996a5bbf20
</content>
</entry>
<entry>
<title>meta-evb: increment CONF_VERSION</title>
<updated>2021-08-10T21:56:33+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-08-10T10:48:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=eebb12c77929975c142fa00e3eb1ff4cd21a75ac'/>
<id>urn:sha1:eebb12c77929975c142fa00e3eb1ff4cd21a75ac</id>
<content type='text'>
Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I2ca490f59630039696f7d1c8086520aa805a7e36
</content>
</entry>
<entry>
<title>meta-evb: prep for new override syntax</title>
<updated>2021-08-10T21:56:33+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-08-06T14:03:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=ed2ee5d25d6f756fe721e16b39aabbd475d982d9'/>
<id>urn:sha1:ed2ee5d25d6f756fe721e16b39aabbd475d982d9</id>
<content type='text'>
Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I7a755976c2144356314faef7cf1f226ae18dc884
</content>
</entry>
<entry>
<title>Remove redundant code to set root password</title>
<updated>2021-08-10T11:13:37+00:00</updated>
<author>
<name>Joseph Reynolds</name>
<email>joseph-reynolds@charter.net</email>
</author>
<published>2021-08-04T15:01:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=516363e50000bf4c41a32dbe521ce50727eaded2'/>
<id>urn:sha1:516363e50000bf4c41a32dbe521ce50727eaded2</id>
<content type='text'>
Background: The OpenBmc project default root account password is set
in meta-phosphor/conf/distro/include/phosphor-defaults.inc and can be
customized in each layer's local.conf file.

Many of these local.conf.sample files had redundant code to set the
password, which probably should not have been there.  Removing them
allows the defaults in phosphor-defaults.inc to take effect.

Tested: No.  Only meta-ibm was tested.

Signed-off-by: Joseph Reynolds &lt;joseph-reynolds@charter.net&gt;
Change-Id: I76dce00d269d7afa005d7bcfd63f846d3cf45596
</content>
</entry>
<entry>
<title>treewide: Remove obsolete image-mklibs class</title>
<updated>2021-06-07T06:22:06+00:00</updated>
<author>
<name>William A. Kennington III</name>
<email>wak@google.com</email>
</author>
<published>2021-05-27T22:36:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=76f91bca10fbb88a5e376f4a338baa30778f9ec8'/>
<id>urn:sha1:76f91bca10fbb88a5e376f4a338baa30778f9ec8</id>
<content type='text'>
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 &lt;wak@google.com&gt;
</content>
</entry>
<entry>
<title>meta-evb-nuvoton: add symlinks for machine-conf for setup</title>
<updated>2021-04-12T18:51:03+00:00</updated>
<author>
<name>Patrick Williams</name>
<email>patrick@stwcx.xyz</email>
</author>
<published>2021-02-20T01:33:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/tmp/openbmc.git/commit/?id=39c9d3d1bbd05b16016ec6f8044dea8e60d96aff'/>
<id>urn:sha1:39c9d3d1bbd05b16016ec6f8044dea8e60d96aff</id>
<content type='text'>
The 'setup' script looks for machine config files being present
to know that the meta-layer contains a valid machine for OpenBMC.
The nuvoton EVBs are split between meta-nuvoton for the base support
and meta-evb-nuvoton for "EVB on Phosphor" support.

Add symlinks for the machine config files from meta-nuvoton into
meta-evb-nuvoton so that setup recognizes them as valid machines, but
using the phosphor layers.

Signed-off-by: Patrick Williams &lt;patrick@stwcx.xyz&gt;
Change-Id: I871432047979f8a7c3d1b836633a5dc74864b6fa
</content>
</entry>
</feed>
