subtree updates

poky: da0ce760c5..14c5392fde:
  Andrej Valek (1):
        busybox: add tmpdir option into mktemp applet

  Anuj Mittal (2):
        documentation: prepare for 3.3.2 release
        poky.conf: bump version for 3.3.2 hardknott release

  Asfak Rahman (1):
        openssh: Remove temporary keys before generating new ones

  Bruce Ashfield (6):
        linux-yocto/5.10: update to v5.10.47
        linux-yocto/5.4: update to v5.4.129
        linux-yocto/5.10: scsi-debug needs scsi-disk
        linux-yocto-dev: base AUTOREV on specified version
        kernel-devsrc: fix scripts/prepare for ARM64
        kernel-devsrc: fix scripts prepare for powerpc

  Changqing Li (2):
        libconvert-asn1-perl: fix CVE-2013-7488
        boost-build-native: workaround one rarely hang problem on fedora34

  Florian Amstutz (1):
        devtool: deploy-target: Fix preserving attributes when using --strip

  Kai Kang (1):
        rxvt-unicode: fix CVE-2021-33477

  Khairul Rohaizzat Jamaluddin (2):
        curl: Fix CVE-2021-22898
        curl: Fix CVE-2021-22897

  Marek Vasut (1):
        linux-firmware: Package RSI 911x WiFi firmware

  Mingli Yu (1):
        perl: correct libpth and glibpth

  Richard Purdie (9):
        oeqa/selftest/runcmd: Tweal test timeouts
        sstate/staging: Handle directory creation race issue
        oeqa/selftest/archiver: Allow tests to ignore empty directories
        runqemu: Remove potential lock races around tap device handling
        glibc-testsuite: Fix build failures when directly running recipe
        oeqa/selftest/multiprocesslauch: Fix test race
        dwarfsrcfiles: Avoid races over debug-link files
        bitbake: data_smart/parse: Allow ':' characters in variable/function names
        bitbake: data_smart: Allow colon in variable expansion regex

  Vinay Kumar (1):
        binutils: Fix CVE-2021-20197

  Wadim Egorov (1):
        xserver-xorg: Fix builds without glx

  wangmy (2):
        go: upgrade 1.16.3 -> 1.16.4
        go: upgrade 1.16.4 -> 1.16.5

  zhengruoqin (1):
        busybox: upgrade 1.33.0 -> 1.33.1

meta-raspberrypi: 064f5404ea..9d372828ba:
  Martin Jansa (1):
        python3-adafruit-*: fix branch parameter

meta-openembedded: c51e79dd85..5a4b2ab29d:
  Adrian Zaharia (1):
        ntp: fix ntpdate to wait for subprocesses

  Akifumi Chikazawa (1):
        openvpn: add CVE-2020-7224 and CVE-2020-27569 to allowlist

  Andreas Müller (1):
        mariadb: Fix configure

  Armin Kuster (1):
        hiawatha: fix url.

  Changqing Li (1):
        nginx: fix CVE-2021-23017

  Gianfranco (3):
        vboxguestdrivers: upgrade 6.1.18 -> 6.1.20
        vboxguestdrivers: upgrade 6.1.20 -> 6.1.22
        vboxguestdrivers: add a fix for build failure with kernel 5.13

  Joe Slater (1):
        python3-pillow: fix CVE-2021-34552

  Kai Kang (1):
        mariadb: fix failures to start install_db.service

  Khem Raj (3):
        mariadb: Upgrade to 10.5.10
        mariadb: Include missing sys/type.h for ssize_t
        mariadb: Fix build with clang/musl

  Leon Anavi (1):
        python3-urllib3: Upgrade 1.26.4 -> 1.26.5

  Li Wang (1):
        apache2: fix CVE-2020-13950 CVE-2020-35452 CVE-2021-26690 CVE-2021-26691 CVE-2021-30641

  Masaki Ambai (1):
        nss: add CVE-2006-5201 to allowlist

  Sam Van Den Berge (1):
        libiio: fix installing libiio when python3 bindings are enabled

  Tony Tascioglu (2):
        redis: fix CVE-2021-29477
        redis: fix CVE-2021-29478

  Trevor Gamblin (1):
        python3-django: upgrade 3.2.4 -> 3.2.5 (fix CVE-2021-35042)

  Zoltán Böszörményi (2):
        mariadb: Use qemu to run cross-compiled binaries
        mariadb: Upgrade to 10.5.11

  massimo toscanelli (1):
        sysbench: fix memory test

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I1321700b087985ab9b27f8f44cc89c8ef8d27e5f
97 files changed
tree: 9ed47243cc39eab7060b00fe3a2423ab7a11cf67
  1. .github/
  2. meta-alibaba/
  3. meta-amd/
  4. meta-ampere/
  5. meta-arm/
  6. meta-aspeed/
  7. meta-bytedance/
  8. meta-evb/
  9. meta-facebook/
  10. meta-fii/
  11. meta-google/
  12. meta-hpe/
  13. meta-hxt/
  14. meta-ibm/
  15. meta-ingrasys/
  16. meta-inspur/
  17. meta-intel-openbmc/
  18. meta-inventec/
  19. meta-lenovo/
  20. meta-microsoft/
  21. meta-nuvoton/
  22. meta-openembedded/
  23. meta-openpower/
  24. meta-phosphor/
  25. meta-portwell/
  26. meta-qualcomm/
  27. meta-quanta/
  28. meta-raspberrypi/
  29. meta-security/
  30. meta-supermicro/
  31. meta-wistron/
  32. meta-x86/
  33. meta-xilinx/
  34. meta-yadro/
  35. poky/
  36. .gitignore
  37. .gitreview
  38. .templateconf
  39. MAINTAINERS
  40. openbmc-env
  41. OWNERS
  42. README.md
  43. setup
README.md

OpenBMC

Build Status

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 set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called setup and takes the name of your hardware target as an argument.

The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:

$ . setup <machine> [build_dir]
Target machine must be specified. Use one of:

centriq2400-rep         f0b                     fp5280g2
gsj                     hr630                   hr855xg2
lanyang                 mihawk                  msn
neptune                 nicole                  olympus
olympus-nuvoton         on5263m5                p10bmc
palmetto                qemuarm                 quanta-q71l
romulus                 s2600wf                 stardragon4800-rep2
swift                   tiogapass               vesnin
witherspoon             witherspoon-tacoma      yosemitev2
zaius

Once you know the target (e.g. romulus), source the setup script as follows:

. setup romulus build

For evb-ast2500, please use the below command to specify the machine config, because the machine in meta-aspeed layer is in a BSP layer and does not build the openbmc image.

TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env

4) Build

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 Discord 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 Discord.

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