Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / refs/heads/honister
commit46fc02f3932e37eb07ed7cd23ac96d464c6db55c[log] [tgz]
authorPatrick Williams <patrick@stwcx.xyz>Tue Oct 18 12:34:53 2022 -0500
committerPatrick Williams <patrick@stwcx.xyz>Tue Oct 18 12:35:34 2022 -0500
treeb60616a81b0bbc1012f678b783df7c2e07f72161
parenta515de07dfa9eda7a303af296666e2572e581df7 [diff]
subtree updates

meta-openembedded: 9a0caf5b09..0e6c34f82c:
  Martin Jansa (1):
        ostree: prevent ostree-native depending on target virtual/kernel to provide kernel-module-overlay

  Nicolas Dechesne (1):
        imlib2: update SRC_URI

poky: eff78b3802..fd00d74f47:
  Alexandre Belloni (1):
        pseudo: Fix handling of absolute links

  Anuj Mittal (2):
        poky.conf: bump version for 3.4.4 release
        documentation: update for 3.4.4 release

  Bruce Ashfield (10):
        linux-yocto/5.10: update to v5.10.109
        lttng-modules: update to 2.13.1
        lttng-modules: support kernel 5.18+
        linux-yocto/5.10: features/security: Move x86_64 configs to separate file
        linux-yocto/5.10: update to v5.10.110
        linux-yocto/5.10: base: enable kernel crypto userspace API
        linux-yocto/5.10: update to v5.10.112
        linux-yocto: enable powerpc debug fragment
        linux-yocto/5.10: update to v5.10.113
        yocto-bsps: update to v5.10.113

  Chen Qi (1):
        cases/buildepoxy.py: fix typo

  Davide Gardenal (1):
        rootfs-postcommands: fix symlinks where link and output path are equal

  Dmitry Baryshkov (2):
        linux-firmware: correct license for ar3k firmware
        linux-firmware: upgrade 20220411 -> 20220509

  Felix Moessbauer (1):
        wic/plugins/rootfs: Fix permissions when splitting rootfs folders across partitions

  Joe Slater (1):
        unzip: fix CVE-2021-4217

  Khem Raj (2):
        busybox: Use base_bindir instead of hardcoding /bin path
        linux-yocto: Enable powerpc-debug fragment for ppc64 LE

  Konrad Weihmann (1):
        gmp: add missing COPYINGv3

  Martin Jansa (1):
        license_image.bbclass: close package.manifest file

  Max Krummenacher (2):
        perf: sort-pmuevents: don't drop elements
        perf: sort-pmuevents: allow for additional type qualifiers and storage class

  Michael Opdenacker (1):
        adding missing space in appends

  Ovidiu Panait (1):
        openssl: upgrade 1.1.1l -> 1.1.1n

  Paul Gortmaker (1):
        install/devshell: Introduce git intercept script due to fakeroot issues

  Peter Kjellerstedt (1):
        u-boot: Inherit pkgconfig

  Portia (1):
        volatile-binds: Change DefaultDependencies from false to no

  Rahul Kumar (1):
        neard: Switch SRC_URI to git repo

  Ralph Siemsen (1):
        xz: fix CVE-2022-1271

  Ranjitsinh Rathod (1):
        openssl: Minor security upgrade 1.1.1n to 1.1.1o

  Richard Purdie (14):
        scripts/runqemu: Fix memory limits for qemux86-64
        vim: Upgrade 8.2.4524 -> 8.2.4681
        uninative: Upgrade to 3.6 with gcc 12 support
        tiff: Add marker for CVE-2022-1056 being fixed
        externalsrc/devtool: Fix to work with fixed export funcition flags handling
        libxshmfence: Correct LICENSE to HPND
        alsa-tools: Ensure we install correctly
        shadow-native: Simplify and fix syslog disable patch
        build-appliance-image: Update to honister head revision
        base: Avoid circular references to our own scripts
        base: Drop git intercept
        scripts: Make git intercept global
        scripts/git: Ensure we don't have circular references
        vim: Upgrade 8.2.4681 -> 8.2.4912

  Ross Burton (4):
        bitbake: knotty: display active tasks when printing keepAlive() message
        bitbake: knotty: reduce keep-alive timeout from 5000s (83 minutes) to 10 minutes
        bitbake.conf: mark all directories as safe for git to read
        oeqa/selftest: add test for git working correctly inside pseudo

  wangmy (3):
        linux-firmware: upgrade 20220310 -> 20220411
        lttng-modules: upgrade 2.13.1 -> 2.13.2
        lttng-modules: upgrade 2.13.2 -> 2.13.3

  zhengruoqin (1):
        wireless-regdb: upgrade 2022.02.18 -> 2022.04.08

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

  • 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:

bletchley               gsj                     romulus
dl360poc                kudo                    s2600wf
e3c246d4i               mihawk                  swift
ethanolx                mtjade                  tiogapass
evb-ast2500             nicole                  transformers
evb-ast2600             olympus-nuvoton         witherspoon
evb-npcm750             on5263m5                witherspoon-tacoma
f0b                     p10bmc                  x11spi
fp5280g2                palmetto                yosemitev2
g220a                   qemuarm                 zaius
gbs                     quanta-q71l

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.

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
  • Samer El-Haj-Mahmoud, Arm

Contact