From 67850dd8a1b1cd4d8a7fc0df459944f20f8e68e5 Mon Sep 17 00:00:00 2001 From: Gunnar Mills Date: Mon, 19 Mar 2018 10:17:30 -0500 Subject: Remove references to Barreleye Barreleye is no longer a supported machine. Removed references to Barreleye and replaced them with Zaius as an example machine to build. Change-Id: I37356cd0720f570941b24dd7c0be3e61d67323d6 Signed-off-by: Gunnar Mills --- cheatsheet.md | 6 +++--- yocto-development.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/cheatsheet.md b/cheatsheet.md index 46f3766..4faeeff 100644 --- a/cheatsheet.md +++ b/cheatsheet.md @@ -33,14 +33,14 @@ $ TEMPLATECONF=meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf $ bitbake obmc-phosphor-image ``` -## Building for Barreleye +## Building for Zaius -The Barreleye target is `barreleye`. +The Zaius target is `zaius`. If you are starting from scratch without a `build/conf` directory you can just: ``` $ cd openbmc -$ TEMPLATECONF=meta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/conf . openbmc-env +$ TEMPLATECONF=meta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf . openbmc-env $ bitbake obmc-phosphor-image ``` diff --git a/yocto-development.md b/yocto-development.md index 26ed7a5..cc89483 100644 --- a/yocto-development.md +++ b/yocto-development.md @@ -17,7 +17,7 @@ There are two main use-cases for Yocto in OpenBMC: The first is the easy case, and largely involves picking the system configuration to build before invoking `bitbake`. Examples for [Palmetto](cheatsheet.md#building-for-palmetto) and -[Barreleye](cheatsheet.md#building-for-barreleye) are in the +[Zaius](cheatsheet.md#building-for-zaius) are in the [cheatsheet](cheatsheet.md). The second case can be helped with Yocto's `devtool`. After running -- cgit v1.2.1