Release v1.99.4

[Andrew Jeffery]

A few points and queries:

On Thu, 2017-04-06 at 15:33 -0500, Patrick Williams wrote:
> I released a tag v1.99.4 as our next development milestone towards
> v2.0.  There are 209 commits between v1.99.4 and v1.99.3, plus the
> usual many more commits in sub-repositories we manage.
> 
> Big changes in this tag:
>     * Upgrade from Yocto 2.2 to Yocto 2.1.
>         - This was a major change in Yocto/Bitbake.  They upgraded
>           all bitbake scripts from python2 to python3.

Building OpenBMC on "small" systems (e.g. systems with less than 8GiB
of RAM) may fail, as we hit a libstdc++ bug as a result of the upgrade:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80290

>     * Power9 systems use OpenFSI and compiled application for processor
>       control instead of shell scripts.

As a note, pdbg has been "moved" to the debug tarball and is no-longer
available on the system out-of-the-box.

>     * Elimination of "debug mode" in favor of systemd targets:
>         - External FSI control for Cronus is done by systemd targets.
>         - Automatic reboot of the host can be disabled independently
>           by systemd targets.  This leaves the system in quiesce state
>           when the host-watchdog fail or checkstop detection occurs.

Patrick: Do you have a link to documentation of these targets? Ideally
these announcements would also provide these pointers.

>     * LED management is refactored out of 'skeleton' and old
>       /org/openbmc interfaces are removed.
>     * Soft power-off should be supported.
>         - This allows the host OS to gracefully shutdown on a power-off
>           request.

Again, is there documentation?

Cheers,

Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170407/9f9e9e33/attachment-0001.sig>