Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 32cc5c1f5be9b95ed6ae62eb76f5f06afbd18805
commit32cc5c1f5be9b95ed6ae62eb76f5f06afbd18805[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Tue Sep 01 10:25:32 2020 -0500
committerAndrew Geissler <geissonator@yahoo.com>Tue Sep 01 14:09:43 2020 -0500
tree33e0b2e9c0a458092d103efc1ea619c51b9009a6
parent1ee6bb5418787ac573e6f6edaccc99cfd11edeea [diff]
nuvoton: enable KERNEL_DANGLING_FEATURES_WARN_ONLY

Uptream yocto recently added some new code which enforces
kernel feature validation. The commit which did this is:
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=095175595d9f28d5a0eb7ea520c9af0100bb8dfd

This caused OpenBMC builds to start failing with the following:
| ERROR: Feature 'phosphor-gpio-keys' not found, this will cause configuration failures.
| ERROR: Check the SRC_URI for meta-data repositories or directories that may be missing
| ERROR: Set KERNEL_DANGLING_FEATURES_WARN_ONLY to ignore this issue

OpenBMC does not utilize this aspect of the kernel-yocto.bbclass
so make it a warning only.

Tested:
Verified that the resultant build still had the expected CONFIG
options set in the linux-nuvoton .config file

See openbmc/openbmc#3690

(From meta-phosphor rev: 75a6424eec93729fd40154413b1a350b9f10fe8b)

Change-Id: I12bf3857601f186300d3b1c56c490be6e6582dda
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: 33e0b2e9c0a458092d103efc1ea619c51b9009a6
  1. .github/
  2. meta-arm/
  3. meta-aspeed/
  4. meta-bytedance/
  5. meta-evb/
  6. meta-facebook/
  7. meta-google/
  8. meta-hxt/
  9. meta-ibm/
  10. meta-ingrasys/
  11. meta-inspur/
  12. meta-intel/
  13. meta-inventec/
  14. meta-lenovo/
  15. meta-mellanox/
  16. meta-microsoft/
  17. meta-nuvoton/
  18. meta-openembedded/
  19. meta-openpower/
  20. meta-phosphor/
  21. meta-portwell/
  22. meta-qualcomm/
  23. meta-quanta/
  24. meta-raspberrypi/
  25. meta-security/
  26. meta-x86/
  27. meta-xilinx/
  28. meta-yadro/
  29. poky/
  30. bitbake ⇨ poky/bitbake/
  31. LICENSE ⇨ poky/LICENSE
  32. meta ⇨ poky/meta
  33. meta-poky ⇨ poky/meta-poky/
  34. meta-skeleton ⇨ poky/meta-skeleton
  35. oe-init-build-env ⇨ poky/oe-init-build-env
  36. scripts ⇨ poky/scripts/
  37. .gitignore
  38. .gitreview
  39. .templateconf
  40. MAINTAINERS
  41. openbmc-env
  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         nicole                     stardragon4800-rep2
f0b                     olympus                    swift
fp5280g2                olympus-nuvoton            tiogapass
gsj                     on5263m5                   vesnin
hr630                   palmetto                   witherspoon
hr855xg2                qemuarm                    witherspoon-128
lanyang                 quanta-q71l                witherspoon-tacoma
mihawk                  rainier                    yosemitev2
msn                     romulus                    zaius
neptune                 s2600wf

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