Gitiles
Code Review Sign In
gerrit.openbmc.org / premsjha / op-build / b06624797accdd5ad21d154bfdfaba718eb229ac
commitb06624797accdd5ad21d154bfdfaba718eb229ac[log] [tgz]
authorStewart Smith <stewart@linux.vnet.ibm.com>Thu Jun 22 13:45:33 2017 +1000
committerStewart Smith <stewart@linux.vnet.ibm.com>Thu Jun 22 13:49:49 2017 +1000
treef7b1eb3ac7174d32663acbd35c5e0cacd4b989d3
parent79aae65c0c3a8a1dd5038be3d1aa88addd37fd09 [diff]
Redbud platform: temporary variant of Witherspoon

Witherspoon comes in two variants: 6GPU and 4GPU.

These are referred to as Sequoia and Redbud.

There are minor differences (in how the NVLink bricks are wired up)
that we should be able to handle mostly 'transparently' in firmware.
The current situation is that we need a separate Redbud build that hard
codes some things in skiboot while we wait for Hostboot to populate HDAT
correctly.

Notably, the same image will *NOT* curretly work on Sequoia and Redbud,
which is why we add a redbud platform here.

It is likely that this platform will disappear in a couple of weeks.

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
2 files changed
tree: f7b1eb3ac7174d32663acbd35c5e0cacd4b989d3
  1. ci/
  2. dl/
  3. openpower/
  4. output/
  5. buildroot
  6. .gitignore
  7. .gitmodules
  8. CONTRIBUTING.md
  9. LICENSE
  10. NOTICE
  11. op-build-env
  12. 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.

Development

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

Mailing list: openpower-firmware@lists.ozlabs.org
Info/Subscribe: https://lists.ozlabs.org/listinfo/openpower-firmware
Archives: https://lists.ozlabs.org/pipermail/openpower-firmware/

Building an image

To build an image for a Palmetto system:

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

There are also default configurations for other platforms in openpower/configs/ such as Habanero and Firestone.

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.

Dependencies for 64-bit Ubuntu/Debian systems

  1. Install Ubuntu (>= 14.04) or Debian (>= 7.5) 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 \
   build-essential g++ git bison flex unzip \
   libssl-dev libxml-simple-perl libxml-sax-perl libxml2-dev libxml2-utils xsltproc \
   wget bc

Dependencies for 64-bit Fedora systems

  1. Install Fedora 25 64-bit (older Fedora should also work).

  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-bignum "perl(XML::Simple)" \
   "perl(YAML)" "perl(XML::SAX)" "perl(Fatal)" "perl(Thread::Queue)" \
   "perl(Env)" "perl(XML::LibXML)" "perl(Digest::SHA1)" libxml2-devel \
   which wget unzip tar cpio python bzip2 bc findutils ncurses-devel