Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 730fed8278b2092d2b0079dff74d81131438cb76
commit730fed8278b2092d2b0079dff74d81131438cb76[log] [tgz]
authorAndrew Geissler <geissonator@gmail.com>Wed Sep 19 09:22:27 2018 -0700
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Mon Sep 24 15:39:23 2018 -0400
tree9314ff103fe68bfb0d1709726092eacca95ee62f
parent4028f33b111bb4e66493732d9c99f1f6a6fb1744 [diff]
python: don't sort the manifest in create_manifest

Instead of sorting the entire manifest when it is updated, use
OrderedDict to preserve the order of fields.This means that
packages can be ordered in the manifest to allow non-trivial
FILES assignments (such as a package that picks up pieces of
other packages)

The manifest has been regenerated with the new stable ordering, and
distutils-staticdev moved above distutils so the packaging rules work as
expected.

This is a backport of the same changes done by Ross Burton for python3

Changes since v1:
- Moved distutils-staticdev above distutils so packaging rules work
as expected.
Changes since v2:
- Rebase

(From OE-Core rev: 3c62c42ebde9dd4acdc74c56160d6ce8639b497c)

(From poky rev: b0f5feea01646613626fca99b8e632ab712eaca2)

Change-Id: If5cb97356feffd91ad919e07a3820c0184166c52
Signed-off-by: Andrew Geissler <geissonator@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2 files changed
tree: 9314ff103fe68bfb0d1709726092eacca95ee62f
  1. meta-arm/
  2. meta-aspeed/
  3. meta-evb/
  4. meta-google/
  5. meta-ibm/
  6. meta-ingrasys/
  7. meta-intel/
  8. meta-inventec/
  9. meta-mellanox/
  10. meta-nuvoton/
  11. meta-openembedded/
  12. meta-openpower/
  13. meta-phosphor/
  14. meta-portwell/
  15. meta-qualcomm/
  16. meta-quanta/
  17. meta-raspberrypi/
  18. meta-security/
  19. meta-x86/
  20. poky/
  21. bitbake ⇨ poky/bitbake/
  22. LICENSE ⇨ poky/LICENSE
  23. meta ⇨ poky/meta
  24. meta-poky ⇨ poky/meta-poky/
  25. oe-init-build-env ⇨ poky/oe-init-build-env
  26. scripts ⇨ poky/scripts/
  27. .gitignore
  28. .gitreview
  29. .templateconf
  30. MAINTAINERS
  31. openbmc-env
  32. README.md
  33. 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 23
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake
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

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

  • REST Management
  • IPMI
  • SSH based SOL
  • Power and Cooling Management
  • Event Logs
  • Zeroconf discoverable
  • Sensors
  • Inventory
  • LED Management
  • Host Watchdog
  • Simulation
  • Code Update Support for multiple BMC/BIOS images
  • POWER On Chip Controller (OCC) Support

Features In Progress

  • Full IPMI 2.0 Compliance with DCMI
  • Verified Boot
  • HTML5 Java Script Web User Interface
  • BMC RAS

Features Requested but need help

  • OpenCompute Redfish Compliance
  • OpenBMC performance monitoring
  • cgroup user management and policies
  • Remote KVM
  • Remote USB
  • OpenStack Ironic Integration
  • QEMU enhancements

Finding out more

Dive deeper in to OpenBMC by opening the docs repository.

Contact