Gitiles
Code Review Sign In
gerrit.openbmc.org / premsjha / op-build / a673c656c8e73ed872f8a7754e4c80c7a8e332d0
commita673c656c8e73ed872f8a7754e4c80c7a8e332d0[log] [tgz]
authorJayanth Othayoth <ojayanth@in.ibm.com>Wed Jul 06 01:30:30 2022 -0500
committerJayanth Othayoth <ojayanth@in.ibm.com>Thu Jul 07 23:56:02 2022 -0500
treebe6099216e3d4a46182d2b3ec1816048f5cd9a6f
parent235ed85658efe3ca8b53129efeb3949979598201 [diff]
pdata: version bump 3e2938d..1ae8abf

Jayanth Othayoth (3):
     data/p10: ATTR_SYS_CLOCK_DECONFIG_STATE size update
     data/p10: ATTR_SYS_CLOCK_DECONFIG_STATE preserved_attrs_list
           updates
     data/p10: Added ATTR_SYS_CLOCK_DECONFIG_STATE

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
1 file changed
tree: be6099216e3d4a46182d2b3ec1816048f5cd9a6f
  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