Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / b58112e5af484d9314f6a4487b1bc8b292f952ef
commitb58112e5af484d9314f6a4487b1bc8b292f952ef[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Thu Mar 07 11:16:36 2024 -0600
committerPatrick Williams <patrick@stwcx.xyz>Fri Mar 08 11:31:06 2024 +0000
treed45e1f67b4c5a28e336b3cc9943934d41c902cd6
parent79cfa849badfe790acf152757b015db22c0e9800 [diff]
subtree updates

meta-raspberrypi: 95a9103f91..92a9b7a012:
  Michał Kluska (1):
        rpi-base: Added missing HiFiBerry

meta-openembedded: 9f0e513211..a0237019f5:
  Alexander Stein (1):
        libkcapi: Update HOMEPAGE url

  Changqing Li (4):
        syslog-ng: upgrade 4.0.1 -> 4.6.0
        multipath-tools: upgrade 0.9.3 -> 0.9.8
        nodejs: upgrade 20.11.0 -> 20.11.1
        postgresql: upgrade 15.5 -> 16.2

  Joe Slater (1):
        googletest: allow for shared libraries

  Khem Raj (17):
        python3-fastjsonschema: Add missing ptest deps
        python3-gpiod: Tests rely on configfs support in kernel
        python3-pyzmq: Add missing dep on python3-unixadmin for ptests
        python3-betamax: Upgrade to 0.9.0
        libgpiod: Tests rely on configfs support in kernel
        keyutils: Add missing rdep for ptests
        fuse3: Make kmod as a recommendation instead of rdep for ptests
        drbd-utils: Disable warnings as errors
        influxdb: Define GOPROXY
        crucible: Define GOPROXY
        syzkaller: Fix build with go 1.21
        e2tools: Delete unneeded files from ptest package
        ptest-packagelists-meta-oe: Move libgpiod out of PTESTS_PROBLEMS_META_OE
        ptest-packagelists-meta-python: Move py3-libgpiod out of PTESTS_PROBLEMS_META_PYTHON
        pgpool2: Upgrade to 4.5.1
        pgpool2: Fix build with postgresql 16+
        emacs: Add packageconfig for selinux support

  Krupal Ka Patel (1):
        python3-aiohappyeyeballs: Correct the typo of BBCLASSEXTEND

  Markus Volk (3):
        folks: update 0.15.6 -> 0.15.7
        mozjs-115: update 115.6.0 -> 115.8.0
        polkit: update 123 -> 124

  Martin Jansa (3):
        ristretto: use python3native and depend on glib-2.0-native, python3-packaging-native
        xfce4-notifyd: use python3native and depend on python3-packaging-native
        fuse3: use 4 spaces for indentation

  Mingli Yu (1):
        nlohmann-json: Upgrade to 3.11.3

  Randolph Sapp (1):
        glmark2: add upstream patch to not care about stencil config

  Ulrich Ölmann (1):
        signing.bbclass: fix typos

  Xiangyu Chen (3):
        iperf3: upgrade 3.15 -> 3.16
        grpc: upgrade 1.60.0 -> 1.60.1
        drbd-utils: upgrade 9.22.0 -> 9.27.0

  Yi Zhao (7):
        openipmi: fix do_configure error when using dash
        cryptsetup: upgrade 2.6.1 -> 2.7.0
        layer.conf: Add nativesdk-libdevmapper PREFERRED_RPROVIDER
        krb5: upgrade 1.20.2 -> 1.21.2
        postfix: upgrade 3.7.3 -> 3.8.5
        openldap: upgrade 2.5.16 -> 2.6.7
        openvpn: upgrade 2.6.7 -> 2.6.9

  Yoann Congal (3):
        drbd-utils: Drop a duplicated line in DESCRIPTION
        drbd-utils: Fix a udev rule reproducibility
        toybox-inittab: Fix serial getty reproducibility

  alperak (9):
        python3-google-auth: upgrade 2.28.0 -> 2.28.1
        python3-netaddr: upgrade 0.10.1 -> 1.2.1 and add ptest
        ptest-packagelists-meta-python: Move python3-xlrd from PTESTS_PROBLEMS_META_PYTHON to PTESTS_FAST_META_PYTHON
        python3-wrapt: add ptest
        python3-freezegun: add recipe and add ptest
        python3-dateutil: upgrade 2.8.2 -> 2.9.0
        python3-types-python-dateutil: add recipe
        python3-arrow: add ptest, update backend and runtime dependencies
        python3-marshmallow: upgrade 3.20.2 -> 3.21.1 and add ptest

poky: 25d60ac6f6..7165c23237:
  Alexander Kanavin (48):
        xz: correct upstream version check
        python3-sphinxcontrib-jquery: add a recipe and make python3-sphinx-rtd-theme depend on it
        acl: upgrade 2.3.1 -> 2.3.2
        appstream: upgrade 1.0.0 -> 1.0.2
        boost: upgrade 1.83.0 -> 1.84.0
        btrfs-tools: upgrade 6.5.3 -> 6.7.1
        dnf: upgrade 4.18.2 -> 4.19.0
        diffoscope: upgrade 253 -> 259
        ell: upgrade 0.62 -> 0.63
        elfutils: upgrade 0.189 -> 0.191
        epiphany: upgrade 45.1 -> 45.3
        gettext: upgrade 0.22.4 -> 0.22.5
        glib-2.0: upgrade 2.78.3 -> 2.78.4
        glib-networking: upgrade 2.78.0 -> 2.78.1
        kmscube: upgrade to latest revision
        libbsd: upgrade 0.11.8 -> 0.12.1
        libdnf: update 0.72.0 -> 0.73.0
        libpciaccess: upgrade 0.17 -> 0.18
        libpcre2: upgrade 10.42 -> 10.43
        librepo: update 1.16.0 -> 1.17.0
        libusb1: upgrade 1.0.26 -> 1.0.27
        libxml2: upgrade 2.11.5 -> 2.12.5
        linux-firmware: upgrade 20231211 -> 20240220
        librsvg: upgrade 2.56.3 -> 2.57.1
        lsof: upgrade 4.98.0 -> 4.99.3
        man-pages: upgrade 6.05.01 -> 6.06
        mc: upgrade 4.8.30 -> 4.8.31
        mesa: upgrade 24.0.1 -> 24.0.2
        minicom: upgrade 2.8 -> 2.9
        nghttp2: upgrade 1.59.0 -> 1.60.0
        orc: upgrade 0.4.37 -> 0.4.38
        puzzles: upgrade to latest revision
        piglit: upgrade to latest revision
        python3-build: upgrade 1.0.3 -> 1.1.1
        python3-dtschema: upgrade 2023.7 -> 2024.2
        python3-jsonschema: upgrade 4.17.3 -> 4.21.1 and add new dependencies
        python3-ruamel-yaml: upgrade 0.17.35 -> 0.18.6
        python3-setuptools: upgrade 69.0.3 -> 69.1.1
        python3-wcwidth: upgrade 0.2.12 -> 0.2.13
        repo: upgrade 2.41 -> 2.42
        shaderc: update 2023.7 -> 2023.8
        systemd: upgrade 255.1 -> 255.4
        ttyrun: upgrade 2.30.0 -> 2.31.0
        taglib: upgrade 1.13.1 -> 2.0 and add utfcpp recipe to support that
        update-rc.d: upgrade to latest revision
        vala: upgrade 0.56.13 -> 0.56.15
        vulkan: upgrade 1.3.268.0 -> 1.3.275.0
        webkitgtk: upgrade 2.42.2 -> 2.42.5

  Bruce Ashfield (3):
        linux-yocto/cfg/6.6: drop CONFIG_DEBUG_CREDENTIALS
        linux-yocto/6.6: update to v6.6.20
        linux-yocto/6.6: update CVE exclusions

  Changqing Li (3):
        rxvt-unicode: Fix installing of terminfo
        systemd: fix dead link /var/log/README
        go: filter out build specific path from the linker flags

  Chen Qi (2):
        systemd: use RDEPENDS for systemd-vconsole-setup
        systemd: remove systemd-bus-proxy settings

  Christian Taedcke (1):
        image_types.bbclass: fix vfat image names

  Eilís 'pidge' Ní Fhlannagáin (6):
        qemurunner.py: Fix error on calls to run_monitor
        screenshot-tests: Add initial screenshot test png files for core-image-sato
        oeqa/runtime/login: Proof of concept for screenshot testcases
        oeqa/runtime/login: Exclude qemuriscv64
        oeqa/runtime/login: Add screenshot sample logic/timeout/dbus-wait
        sstatetests.py: Add testing for correct sstate permissions

  Fabio Estevam (1):
        u-boot: Move UBOOT_INITIAL_ENV back to u-boot.inc

  Geoff Parker (1):
        ref-manual: variables: adding multiple groups in GROUPADD_PARAM

  Johan Bezem (1):
        ref-manual: variables: correct sdk installation default path

  Jose Quaresma (7):
        go: rework patch to avoid identation
        go: bump 1.21.0
        goarch: disable dynamic linking globally
        oeqa/gotoolchain: set GOPROXY
        go: upgrade 1.21.0 -> 1.21.5
        go: upgrade 1.21.5 -> 1.21.7
        go: bump 1.22.0

  Khem Raj (4):
        mesa,mesa-gl: Fix build when dri3 is not enabled
        linux-yocto: Enable gpio-sim with ptests
        rust: Fix build failure re-appeared on riscv32
        gdb: Upgrade 14.1 -> 14.2

  Luca Ceresoli (2):
        ref-manual: tasks: do_cleanall: recommend using '-f' instead
        ref-manual: tasks: do_cleansstate: recommend using '-f' instead for a shared sstate

  Markus Volk (1):
        gtk+3: update 3.24.38 -> 3.24.41

  Michael Opdenacker (4):
        core-image-full-cmdline: add package-management
        bitbake: utils: remove BB_ENV_PASSTHROUGH from preserved_envvars()
        dev-manual: packages: fix capitalization
        manuals: document VIRTUAL-RUNTIME variables

  Randy MacLeod (1):
        valgrind: skip intermittently failing ptests

  Richard Purdie (9):
        no-gplv3: Tweak for packagemangement in core-image-full-cmdline
        qemu: Replace workaround with proper usermode fix for shmat
        bitbake: fetch/git: Avoid clean upon failure
        go: Further tweak indentation in patch
        go: Drop linkmode with nativesdk/cross-canadian
        libpng: Update SRC_URI to avoid redirects
        oeqa/runtime/login: Various code improvements and fixes
        oeqa/runtime/login: Mask out the mouse panel icon for now
        oeqa/runtime/login: Fix dbus-wait timeout and loop conditional

  Robert P. J. Day (1):
        python3-cryptography_42.0.5.bb: delete redundant ptest packaging

  Ross Burton (2):
        Add genericarm64 MACHINE
        rxvt: add rxvt to desktop entry name

  Simone Weiß (4):
        coreutils: backport patch to fix heap overflow in split
        qemu: backport patch for ui/clipboard issue
        ref-manual: classes: add cve status check for oe.qa
        contributor-guide: add notes for tests

  Tim Orling (1):
        python3-hypothesis: upgrade 6.98.12 -> 6.98.15

  Trevor Woerner (2):
        bmaptool: now part of Yocto Project
        dev-manual: bmaptool: rename

  Yi Zhao (1):
        expat: upgrdae 2.6.0 -> 2.6.1

  Yoann Congal (1):
        bitbake: prserv/serv: Fix a PID file removal race on prserv stop

Change-Id: Ie94e4df79e3d8f68aea3377f816d7106987a05f8
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
380 files changed
tree: d45e1f67b4c5a28e336b3cc9943934d41c902cd6
  1. .github/
  2. meta-amd/
  3. meta-ampere/
  4. meta-arm/
  5. meta-aspeed/
  6. meta-asrock/
  7. meta-bytedance/
  8. meta-delta/
  9. meta-evb/
  10. meta-facebook/
  11. meta-fii/
  12. meta-google/
  13. meta-hpe/
  14. meta-ibm/
  15. meta-ieisystems/
  16. meta-ingrasys/
  17. meta-intel-openbmc/
  18. meta-inventec/
  19. meta-nuvoton/
  20. meta-openembedded/
  21. meta-openpower/
  22. meta-phosphor/
  23. meta-qualcomm/
  24. meta-quanta/
  25. meta-raspberrypi/
  26. meta-security/
  27. meta-supermicro/
  28. meta-tyan/
  29. meta-ufispace/
  30. meta-wistron/
  31. meta-yadro/
  32. poky/
  33. .templateconf ⇨ poky/.templateconf
  34. bitbake ⇨ poky/bitbake/
  35. LICENSE ⇨ poky/LICENSE
  36. meta ⇨ poky/meta
  37. meta-poky ⇨ poky/meta-poky/
  38. meta-skeleton ⇨ poky/meta-skeleton
  39. oe-init-build-env ⇨ poky/oe-init-build-env
  40. scripts ⇨ poky/scripts/
  41. .eslintrc.json
  42. .gitignore
  43. .gitreview
  44. openbmc-env
  45. OWNERS
  46. README.md
  47. setup
README.md

OpenBMC

Build Status

OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.

Setting up your OpenBMC project

1) Prerequisite

See the Yocto documentation for the latest requirements

Ubuntu

sudo apt install git python3-distutils gcc g++ make file wget \
    gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2

Fedora

sudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio \
    hostname file diffutils diffstat lz4 wget zstd rpcgen patch

2) Download the source

git clone https://github.com/openbmc/openbmc
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:

bletchley               mori                    s8036
dl360poc                mtjade                  swift
e3c246d4i               mtmitchell              tatlin-archive-x86
ethanolx                nicole                  tiogapass
evb-ast2500             olympus-nuvoton         transformers
evb-ast2600             on5263m5                vegman-n110
evb-npcm750             p10bmc                  vegman-rx20
f0b                     palmetto                vegman-sx20
fp5280g2                qcom-dc-scm-v1          witherspoon
g220a                   quanta-q71l             witherspoon-tacoma
gbs                     romed8hm3               x11spi
greatlakes              romulus                 yosemitev2
gsj                     s2600wf                 zaius
kudo                    s6q
lannister               s7106

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

. setup romulus

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.

Will OpenBMC run on my Acme Server Corp. XYZ5000 motherboard?

This is a common question, particularly regarding boards from popular COTS (commercial off-the-shelf) vendors such as Supermicro and ASRock. You can see the list of supported boards by running . setup (with no further arguments) in the root of the OpenBMC source tree. Most of the platforms supported by OpenBMC are specialized servers operated by companies running large datacenters, but some more generic COTS servers are supported to varying degrees.

If your motherboard is not listed in the output of . setup it is not currently supported. Porting OpenBMC to a new platform is a non-trivial undertaking, ideally done with the assistance of schematics and other documentation from the manufacturer (it is not completely infeasible to take on a porting effort without documentation via reverse engineering, but it is considerably more difficult, and probably involves a greater risk of hardware damage).

However, even if your motherboard is among those listed in the output of . setup, there are two significant caveats to bear in mind. First, not all ports are equally mature -- some platforms are better supported than others, and functionality on some "supported" boards may be fairly limited. Second, support for a motherboard is not the same as support for a complete system -- in particular, fan control is critically dependent on not just the motherboard but also the fans connected to it and the chassis that the board and fans are housed in, both of which can vary dramatically between systems using the same board model. So while you may be able to compile and install an OpenBMC build on your system and get some basic functionality, rough edges (such as your cooling fans running continuously at full throttle) are likely.

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:

  • Benjamin Fair, Google
  • Patrick Williams, Meta
  • Roxanne Clarke, IBM
  • Sagar Dharia, Microsoft
  • Samer El-Haj-Mahmoud, Arm
  • Terry Duncan, Intel

Contact