From 194ff4f1f5d44b12e9cb06ddafa6adb20174a13c Mon Sep 17 00:00:00 2001 From: Dave Cobbley Date: Wed, 22 Aug 2018 21:40:54 -0400 Subject: [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 --- README.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index f41bbad45..84eabfae9 100644 --- a/README.md +++ b/README.md @@ -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 -`meta-openbmc-machines/meta-[architecture]/meta-[company]/meta-[target]`. +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](https://github.com/openbmc/docs/blob/master/cheatsheet.md) Machine | TEMPLATECONF --------|--------- -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 -- cgit v1.2.1