path: root/
diff options
authorDave Cobbley <>2018-08-22 21:40:54 -0400
committerBrad Bishop <>2018-08-23 12:39:42 -0400
commit194ff4f1f5d44b12e9cb06ddafa6adb20174a13c (patch)
tree823835cd29daf8901a31ac14c7e6534abf199be3 /
parent4feb727cd6b77a68bdaca63e121b378d814f5eaf (diff)
[Subtree] Bring openbmc machines to top level
The new subtree model brings the subtrees up from the openbmc-machines layer. Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0 Signed-off-by: Dave Cobbley <> Signed-off-by: Brad Bishop <>
Diffstat (limited to '')
1 files changed, 6 insertions, 8 deletions
diff --git a/ b/
index f41bbad45..84eabfae9 100644
--- a/
+++ b/
@@ -35,24 +35,22 @@ cd openbmc
### 3) Target your hardware
Any build requires an environment variable known as `TEMPLATECONF` to be set
-to a hardware target. OpenBMC has placed all known hardware targets in a
-standard directory structure
+to a hardware target.
You can see all of the known targets with
-`find meta-openbmc-machines -type d -name conf`. Choose the hardware target and
+`find meta-* -name local.conf.sample`. Choose the hardware target and
then move to the next step. Additional examples can be found in the
[OpenBMC Cheatsheet](
-Palmetto | ```meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf```
-Zaius| ```meta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf```
-Witherspoon| ```meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/conf```
+Palmetto | ```meta-ibm/meta-palmetto/conf```
+Zaius| ```meta-ingrasys/meta-zaius/conf```
+Witherspoon| ```meta-ibm/meta-witherspoon/conf```
As an example target Palmetto
-export TEMPLATECONF=meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf
+export TEMPLATECONF=meta-ibm/meta-palmetto/conf
### 4) Build
OpenPOWER on IntegriCloud