Gitiles
Code Review Sign In
gerrit.openbmc.org / premsjha / op-build / 301cb8933f48909d52cc726c379fb93487560c52
commit301cb8933f48909d52cc726c379fb93487560c52[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Wed Apr 03 10:59:50 2019 +1030
committerJoel Stanley <joel@jms.id.au>Wed Apr 03 11:09:11 2019 +1030
tree6ca704d62bdc38d8a378cf856a1164d2c9e97999
parent59e1b74b6cef5847cb58d62897ac4e9b84a6ecd8 [diff]
kernel: Move to Linux v5.0.5-openpower1

PowerPC changes:

 powerpc/security: Fix spectre_v2 reporting
 powerpc/vdso64: Fix CLOCK_MONOTONIC inconsistencies across Y2038

Defconfigs are regenerated as we are back on the default kernel version,
so the configs do not need to set the kernel series for the headers
package.

Signed-off-by: Joel Stanley <joel@jms.id.au>
15 files changed
tree: 6ca704d62bdc38d8a378cf856a1164d2c9e97999
  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-env
  14. 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 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/. Current POWER8 platforms include Habanero, Firestone, and Garrison. 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 \
   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-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