Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 5896a23a772947bb149670beecf8a7178f78eca6
commit5896a23a772947bb149670beecf8a7178f78eca6[log] [tgz]
authorVernon Mauery <vernon.mauery@linux.intel.com>Tue Apr 23 15:31:51 2019 -0700
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Thu Apr 25 12:59:48 2019 -0400
treeb3b4fe52a0076163080987a19c052ffd79385e42
parent18d6327e2994b5a92c9cc81078b926937e08a2eb [diff]
rebase ipmitool to use upstream git

Upstream ipmitool has been under active development for a while now.
This includes adding the D-Bus interface to ipmitool as an option as
well as a mechanism to set the default interface. So now, building
ipmitool for openbmc is possible directly from upstream. The new patch
that is included in this commit has been pushed upstream and in under
review. It is needed to build in environments that don't have internet
access.

Tested-by: build ipmitool, run it on the BMC and see that it works
           bitbake ipmitool; scp <>/ipmitool <....>:/tmp;
	   /tmp/ipmitool mc info
	   /tmp/ipmitool -h
	   ...
	   Interfaces:
                   open          Linux OpenIPMI Interface
                   imb           Intel IMB Interface
                   lan           IPMI v1.5 LAN Interface
                   lanplus       IPMI v2.0 RMCP+ LAN Interface
                   serial-terminal  Serial Interface, Terminal Mode
                   serial-basic  Serial Interface, Basic Mode
                   dbus          OpenBMC D-Bus interface [default]

(From meta-phosphor rev: c89d95e58d44d0f8e955892b59da2ac0c2beaf91)

Change-Id: I00c15fb8693fca13cdd174661f924e7af684d19d
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
3 files changed
tree: b3b4fe52a0076163080987a19c052ffd79385e42
  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
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