Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / fee4187da774de694d46ca5e65294099461e0030
commitfee4187da774de694d46ca5e65294099461e0030[log] [tgz]
authorBrad Bishop <bradleyb@fuzziesquirrel.com>Sun Jun 09 22:57:35 2019 -0400
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Fri Jun 14 08:18:55 2019 -0400
treee3828a31be35469c485a3f91ea9f4ede12f14041
parent1c65850bff2d16b6790d956b9c6f2a6a7a76022b [diff]
meta-phosphor: ipmid: enable EXTRA_OECONF override

Set the whitelist with the post-parse append operator, so ipmid
bbappends can set EXTRA_OECONF directly.

A simple example illustrates how this helps:
 foo.bb:
  BAR = "def"
  FOO = "abc ${BAR}
 foo.bbappend:
  FOO = "zyx"

FOO would be "zyx"  But if one has:
 foo.bb:
  BAR = "def"
  FOO = "abc"
  FOO_append = " ${BAR}"
 foo.bbappend:
  FOO = "zyx"

FOO would be "zyx def"

This is because bitbake parses recipes and bbappends in multiple
passes - the second pass is when things like the _append operator
and inline python are evaluated.

for more reading:

https://www.yoctoproject.org/docs/latest/bitbake-user-manual/bitbake-user-manual.html#override-style-operation-advantages

(From meta-phosphor rev: bb60cffd406a8a413be0ce70b65d9b3447c95bbf)

Change-Id: I2c9a4eaf65c815ebdf18ff158de75448837872b4
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: e3828a31be35469c485a3f91ea9f4ede12f14041
  1. .github/
  2. meta-arm/
  3. meta-aspeed/
  4. meta-evb/
  5. meta-facebook/
  6. meta-google/
  7. meta-hxt/
  8. meta-ibm/
  9. meta-ingrasys/
  10. meta-inspur/
  11. meta-intel/
  12. meta-inventec/
  13. meta-lenovo/
  14. meta-mellanox/
  15. meta-nuvoton/
  16. meta-openembedded/
  17. meta-openpower/
  18. meta-phosphor/
  19. meta-portwell/
  20. meta-qualcomm/
  21. meta-quanta/
  22. meta-raspberrypi/
  23. meta-security/
  24. meta-x86/
  25. meta-xilinx/
  26. poky/
  27. bitbake ⇨ poky/bitbake/
  28. LICENSE ⇨ poky/LICENSE
  29. meta ⇨ poky/meta
  30. meta-poky ⇨ poky/meta-poky/
  31. meta-skeleton ⇨ poky/meta-skeleton
  32. oe-init-build-env ⇨ poky/oe-init-build-env
  33. scripts ⇨ poky/scripts/
  34. .gitignore
  35. .gitreview
  36. .templateconf
  37. MAINTAINERS
  38. openbmc-env
  39. README.md
  40. 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 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

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-ibm/meta-witherspoon/conf
Romulusmeta-ibm/meta-romulus/conf

As an example target Palmetto

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

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

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.

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

Features In Progress

  • OpenCompute Redfish Compliance
  • User management
  • Virtual media
  • Verified Boot

Features Requested but need help

  • OpenBMC performance monitoring

Finding out more

Dive deeper into OpenBMC by opening the docs repository.

Contact