Gitiles
Code Review Sign In
gerrit.openbmc.org / premsjha / op-build / 68517ebab6494cbfeb0bcf78225186775c7225b2
commit68517ebab6494cbfeb0bcf78225186775c7225b2[log] [tgz]
authorhostboot <hostboot@us.ibm.com>Tue Apr 26 09:08:03 2022 -0500
committerhostboot <hostboot@us.ibm.com>Tue Apr 26 09:08:03 2022 -0500
tree050a8065cff53d883e7051574bc30ef1ebd9db95
parent30818bd82cd71858af69282d61f4035c8e8f05b2 [diff]
op-build ibm-release-fw1020 update 4-26-2022

Changes Included for package hostboot, branch release-fw1020:
a7b2fda - Zach Clark - 2022-04-26 - Reduce PLDM timeout, increase retry numbers at runtime
95f2725 - Greg Still - 2022-04-26 - p10_pstate_parameter_block: remove Pstate -> frequency uplift of 1MHz
4f139c0 - Greg Still - 2022-04-26 - PPB: remove double counting of ECO cores introduced in 128729

Signed-off-by: hostboot <hostboot@us.ibm.com>
1 file changed
tree: 050a8065cff53d883e7051574bc30ef1ebd9db95
  1. ci/
  2. dl/
  3. doc/
  4. openpower/
  5. output/
  6. buildroot
  7. .gitignore
  8. .gitmodules
  9. .travis.yml
  10. CONTRIBUTING.md
  11. LICENSE
  12. NOTICE
  13. op-build
  14. op-build-env
  15. README.md
README.md

OpenPOWER Firmware Build Environment

The OpenPOWER firmware build process uses Buildroot to create a toolchain and build the various components of the PNOR firmware, including Hostboot, Skiboot, OCC, Petitboot etc.

Documentation

https://open-power.github.io/op-build/

See the doc/ directory for documentation source. Contributions are VERY welcome!

Development

Issues, Milestones, pull requests and code hosting is on GitHub: https://github.com/open-power/op-build

See CONTRIBUTING.md for howto contribute code.

Building an image

To build an image for a Blackbird system:

git clone --recursive git@github.com:open-power/op-build.git
cd op-build
./op-build p10ebmc_defconfig && ./op-build

There are also default configurations for other platforms in openpower/configs/. Current POWER9 platforms include Witherspoon, Boston (p9dsu), Romulus, and Zaius.

Buildroot/op-build supports both native and cross-compilation - it will automatically download and build an appropriate toolchain as part of the build process, so you don't need to worry about setting up a cross-compiler. Cross-compiling from a x86-64 host is officially supported.

The machine your building on will need Python 2.7, GCC 6.2 (or later), and a handful of other packages (see below).

Dependencies for 64-bit Ubuntu/Debian systems

  1. Install Ubuntu (>= 18.04) or Debian (>= 9) 64-bit.

  2. Enable Universe (Ubuntu only):

     sudo apt-get install software-properties-common
 sudo add-apt-repository universe

  3. Install the packages necessary for the build:

     sudo apt-get install cscope ctags libz-dev libexpat-dev \
   python language-pack-en texinfo gawk cpio xxd \
   build-essential g++ git bison flex unzip \
   libssl-dev libxml-simple-perl libxml-sax-perl libxml-parser-perl libxml2-dev libxml2-utils xsltproc \
   wget bc rsync

Dependencies for 64-bit Fedora systems

  1. Install Fedora (>= 25) 64-bit.

  2. Install the packages necessary for the build:

     sudo dnf install gcc-c++ flex bison git ctags cscope expat-devel patch \
   zlib-devel zlib-static texinfo "perl(bigint)" "perl(XML::Simple)" \
   "perl(YAML)" "perl(XML::SAX)" "perl(Fatal)" "perl(Thread::Queue)" \
   "perl(Env)" "perl(XML::LibXML)" "perl(Digest::SHA1)" "perl(ExtUtils::MakeMaker)" \
   "perl(FindBin)" "perl(English)" "perl(Time::localtime)" \
   libxml2-devel which wget unzip tar cpio python bzip2 bc findutils ncurses-devel \
   openssl-devel make libxslt vim-common lzo-devel python2 rsync hostname