Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 5ef4dda8ec761fd2c92a114987e2b56cb821cb4f
commit5ef4dda8ec761fd2c92a114987e2b56cb821cb4f[log] [tgz]
authorPatrick Venture <venture@google.com>Tue May 07 14:26:51 2019 -0700
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Wed May 08 19:43:00 2019 -0400
treea46b8a54799f75afdc6a5273148615e6ec66b52b
parentb3331fa8d75fbc54ef020e30bb69af0f5d0e305e [diff]
meta-quanta: layer.conf: set BBFILE_PATTERN

Bitbake uses this regex to associate recipes and bbappends from BBFILES
(which contains recipes and bbappends from -all- layers listed in
bblayers.conf) to this layer.  The association is then used to map the
BBFILE_PRIORITY value for this layer onto the recipes provided by this
layer.

BBFILE_PRIORITY is used to determine which recipe to use when the same
recipe appears in multiple layers.

Without BBFILE_PATTERN set, recipes in this layer will get a default
priority and not the priority specified in BBFILE_PRIORITY.

This layer doesn't set a priority anyway, so functionally this patch is
a noop but it is an improvement from a correctness standpoint, and it
makes a warning go away

Removes warning:
WARNING: No bb files matched BBFILE_PATTERN_quanta ''

(From meta-quanta rev: 745d571bfb21a95152a1f5a112f837f4fa321680)

Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: I3b0f8acdd06ac9842a20a77efc5655966078ce1c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: a46b8a54799f75afdc6a5273148615e6ec66b52b
  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-mellanox/
  14. meta-nuvoton/
  15. meta-openembedded/
  16. meta-openpower/
  17. meta-phosphor/
  18. meta-portwell/
  19. meta-qualcomm/
  20. meta-quanta/
  21. meta-raspberrypi/
  22. meta-security/
  23. meta-x86/
  24. meta-xilinx/
  25. poky/
  26. bitbake ⇨ poky/bitbake/
  27. LICENSE ⇨ poky/LICENSE
  28. meta ⇨ poky/meta
  29. meta-poky ⇨ poky/meta-poky/
  30. meta-skeleton ⇨ poky/meta-skeleton
  31. oe-init-build-env ⇨ poky/oe-init-build-env
  32. scripts ⇨ poky/scripts/
  33. .gitignore
  34. .gitreview
  35. .templateconf
  36. MAINTAINERS
  37. openbmc-env
  38. README.md
  39. 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