commit | e7da8bce4b0e985d2eec172994256687a3fc4caa | [log] [tgz] |
---|---|---|
author | Dave Heller <hellerda@linux.vnet.ibm.com> | Fri Jun 16 18:30:40 2017 -0400 |
committer | Stewart Smith <stewart@linux.vnet.ibm.com> | Thu Jul 27 13:44:17 2017 +1000 |
tree | e07d44d28ba5194b2d3366b663262c0b96ed7290 | |
parent | 84cc655c5a28ed23b442671ccfbd2cf6c578d2c7 [diff] |
Integrate sb-signing-utils into op-build This adds support for building sb-signing-utils from github.com/hellerda. It includes the openpower/package/sb-signing-utils/ directory with Config.in, *.mk, and ./keys directory holding the IBM Imprint keys and README. Build is activated by the presence of BR2_OPENPOWER_SECUREBOOT_ENABLED in the _defconfig. In this patch it is set in habanero_defconfig only. Even with BR2_OPENPOWER_SECUREBOOT_ENABLED, the package will only be built, it will not be activated (i.e. used in PNOR packaging step) until additional patches are added to op-build and openpower-pnor packages. Signed-off-by: Dave Heller <hellerda@linux.vnet.ibm.com> [stewart@linux.vnet.ibm.com: cleaned git history, cherry-picked onto master] Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
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.
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/
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.
Install Ubuntu (>= 14.04) or Debian (>= 7.5) 64-bit.
Enable Universe (Ubuntu only):
sudo apt-get install software-properties-common sudo add-apt-repository universe
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
Install Fedora 25 64-bit (older Fedora should also work).
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