commit	043e75a2e8c9ecd586dfd2ae0ac80a7ceb014ed7	[log] [tgz]
author	Patrick Williams <patrick@stwcx.xyz>	Thu Jul 08 11:39:47 2021 -0500
committer	Patrick Williams <patrick@stwcx.xyz>	Thu Jul 08 12:02:56 2021 -0500
tree	7953ae8b67eb95d27f456f1d3ec9f20b17375575
parent	eee7d70a4dbbd89645098df2397aa3f4e5d8baa0 [diff]

subtree updates

poky: 6ebb33bdac..dc29017614:
  Andrea Adami (1):
        kernel.bbclass: fix do_sizecheck() comparison

  Bruce Ashfield (6):
        kernel-yocto: provide debug / summary information for metadata
        linux-yocto/5.4: update to v5.4.117
        linux-yocto/5.4: update to v5.4.118
        linux-yocto/5.4: update to v5.4.119
        linux-yocto/5.4: update to v5.4.120
        linux-yocto/5.4: update to v5.4.123

  Changqing Li (2):
        unfs3: correct configure option
        pkgconfig: update SRC_URI

  Daniel McGregor (2):
        sstate: Ignore sstate signing key
        lib/oe/gpg_sign.py: Fix gpg verification

  Guillaume Champagne (1):
        image-live.bbclass: order do_bootimg after do_rootfs

  Jasper Orschulko (3):
        expat: fix CVE-2013-0340
        libxml2: Fix CVE-2021-3518
        libx11: Fix CVE-2021-31535

  Kai Kang (1):
        valgrind: fix a typo

  Klaus Heinrich Kiwi (1):
        kernel-fitimage: Don't use unit addresses on FIT

  Lee Chee Yang (6):
        libxml: fix CVE-2021-3517 CVE-2021-3537
        gnutls: fix CVE-2021-20231 CVE-2021-20232
        gstreamer-plugins-good: fix CVE-2021-3497 CVE-2021-3498
        bind: 9.11.22 -> 9.11.32
        ruby: 2.7.1 -> 2.7.3
        python3: fix CVE-2021-23336

  Michael Halstead (1):
        uninative: Upgrade to 3.2 (gcc11 support)

  Ming Liu (2):
        kernel-fitimage.bbclass: fix a wrong conditional check
        initramfs-framework:rootfs: fix wrong indentions

  Ovidiu Panait (2):
        kernel-devicetree: Introduce KERNEL_DTC_FLAGS to pass dtc flags
        variables: Add documentation for KERNEL_DTC_FLAGS

  Richard Purdie (11):
        cve-extra-exclusions.inc: add exclusion list for intractable CVE's
        cve-extra-exclusions: Fix typos
        cve-extra-exclusions.inc: Clean up merged CPE updates
        glibc: Add 8GB VM usage cap for usermode test suite
        grub: Exclude CVE-2019-14865 from cve-check
        oeqa/runtime/rpm: Drop log message counting test component
        linux-firmware: upgrade 20210315 -> 20210511
        bitbake: cooker: Ensure parse_quit thread is closed down
        bitbake: cooker: Explictly shut down the sync thread
        bitbake: cooker: Ensure parser is cleaned up
        bitbake: cooker: Avoid parser deadlocks

  Ross Burton (2):
        cups: whitelist CVE-2021-25317
        package_rpm: pass XZ_THREADS to rpm

  Sana Kazi (1):
        openssh: Add fixes for CVEs reported for openssh

  Steve Sakoman (7):
        expat: set CVE_PRODUCT
        Revert "busybox: make busybox's syslog.cfg depend on VIRTUAL-RUNTIME_base-utils-syslog"
        ref-system-requirements.rst: Add openSUSE Leap 15.2 to list of supported distros
        documentation: prepare for 3.1.9 release
        poky.conf: Add openSUSE Leap 15.2 as a supported distro
        poky.conf: Bump version for 3.1.9 release
        Revert "python3: fix CVE-2021-23336"

  Tim Orling (10):
        python3: upgrade 3.8.2 -> 3.8.3
        python3: upgrade 3.8.3 -> 3.8.4
        python3: upgrade 3.8.4 -> 3.8.5
        python3: upgrade 3.8.5 -> 3.8.6
        python3: upgrade 3.8.6 -> 3.8.7
        python3: upgrade 3.8.7 -> 3.8.8
        powertop: fix aclocal error too many loops
        python3: upgrade 3.8.8 -> 3.8.9
        python3: upgrade 3.8.9 -> 3.8.10
        python3-ptest: add newly discovered missing rdeps

  Tony Tascioglu (2):
        libxml2: Reformat runtest.patch
        libxml2: Add bash dependency for ptests.

  Volker Vogelhuber (1):
        busybox: make busybox's syslog.cfg depend on VIRTUAL-RUNTIME_base-utils-syslog

  akash hadke (1):
        tiff: Add fix for CVE-2020-35521 and CVE-2020-35522

meta-openembedded: 11eae11452..c38d2a74f7:
  Alexander Vickberg (1):
        hostapd: fix building with CONFIG_TLS=internal

  Mikko Rapeli (1):
        ebtables: use bitbake optimization levels

  Sana Kazi (1):
        dnsmasq: Add fixes for CVEs reported for dnsmasq

  akash.hadke (1):
        opencv: Add fix for CVE-2019-5063 and CVE-2019-5064

  wangmy (8):
        exiv2: Fix CVE-2021-29457
        exiv2: Fix CVE-2021-29458
        exiv2: Fix CVE-2021-29463
        exiv2: Fix CVE-2021-3482
        exiv2: Fix CVE-2021-29464
        exiv2: Fix CVE-2021-29470
        exiv2: Fix CVE-2021-29473
        libsdl: Fix CVE-2019-13616

meta-raspberrypi: 77190af02d..f0c75016f0:
  Andrei Gherzan (1):
        layer.conf: Define LAYERDEPENDS

  Martin Jansa (3):
        linux-raspberrypi: allow to change the yocto-kernel-cache branch with LINUX_RPI_KMETA_BRANCH
        linux-raspberrypi-dev: drop protocol=git and add LINUX_RPI_KMETA_BRANCH
        linux-raspberrypi-dev: use static SRCREV when not selected with PREFERRED_PROVIDER_virtual/kernel

  Paul Barker (1):
        linux-raspberrypi-dev: Update for testing v5.10.y

  matt-hammond-bbc (1):
        libva: Fix for when using `userland`

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I3050b4fe814c3036ec5f1914fa7e59584ea4c81c

95 files changed

tree: 7953ae8b67eb95d27f456f1d3ec9f20b17375575

README.md

OpenBMC

The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your server platform.

Setting up your OpenBMC project

1) Prerequisite

Ubuntu 14.04

sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat

Fedora 28

sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake \
    rpcgen perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum
sudo dnf groupinstall "C Development Tools and Libraries"

2) Download the source

git clone git@github.com:openbmc/openbmc.git
cd openbmc

3) Target your hardware

Any build requires an environment variable known as TEMPLATECONF to be set to a hardware target. You can see all of the known targets with find meta-* -name local.conf.sample. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet

Machine	TEMPLATECONF
Palmetto	`meta-ibm/meta-palmetto/conf`
Zaius	`meta-ingrasys/meta-zaius/conf`
Witherspoon	`meta-ibm/meta-witherspoon/conf`
Romulus	`meta-ibm/meta-romulus/conf`

As an example target Romulus

export TEMPLATECONF=meta-ibm/meta-romulus/conf

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

OpenBMC Development

The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here

Build Validation and Testing

Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.

Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.

Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.

Submitting Patches

Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.

Bug Reporting

Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.

Questions

First, please do a search on the internet. There's a good chance your question has already been asked.

For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.

For technical discussions, please see contact info below for IRC and mailing list information. Please don't file an issue to ask a question. You'll get faster results by using the mailing list or IRC.

Features of OpenBMC

Feature List

Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
Full IPMI 2.0 Compliance with DCMI
Code Update Support for multiple BMC/BIOS images
Web-based user interface
REST interfaces
D-Bus based interfaces
SSH based SOL
Remote KVM
Hardware Simulation
Automated Testing
User management
Virtual media

Features In Progress

OpenCompute Redfish Compliance
Verified Boot

Features Requested but need help

OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Technical Steering Committee

The Technical Steering Committee (TSC) guides the project. Members are:

Brad Bishop (chair), IBM
Nancy Yuen, Google
Sai Dasari, Facebook
James Mihm, Intel
Sagar Dharia, Microsoft
Supreeth Venkatesh, Arm

Contact

Mail: openbmc@lists.ozlabs.org https://lists.ozlabs.org/listinfo/openbmc
IRC: #openbmc on freenode.net
Riot: #openbmc:matrix.org