summaryrefslogtreecommitdiffstats
path: root/scripts/lib/bsp/substrate/target/arch/common/README
diff options
context:
space:
mode:
Diffstat (limited to 'scripts/lib/bsp/substrate/target/arch/common/README')
-rw-r--r--scripts/lib/bsp/substrate/target/arch/common/README8
1 files changed, 8 insertions, 0 deletions
diff --git a/scripts/lib/bsp/substrate/target/arch/common/README b/scripts/lib/bsp/substrate/target/arch/common/README
index 928659f302..228c0e2e9d 100644
--- a/scripts/lib/bsp/substrate/target/arch/common/README
+++ b/scripts/lib/bsp/substrate/target/arch/common/README
@@ -65,6 +65,14 @@ You should then be able to build a {{=machine}} image as such:
65 $ source oe-init-build-env 65 $ source oe-init-build-env
66 $ bitbake core-image-sato 66 $ bitbake core-image-sato
67 67
68NOTE: if the '{{=machine}}' machine includes the emgd-driver-bin
69package (i.e. if the emgd version of the xserver is being used), it
70has a proprietary license that must be whitelisted by adding the
71string "license_emgd-driver-bin_1.14" to the LICENSE_FLAGS_WHITELIST
72variable in your local.conf. For example:
73
74 LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.14"
75
68At the end of a successful build, you should have a live image that 76At the end of a successful build, you should have a live image that
69you can boot from a USB flash drive (see instructions on how to do 77you can boot from a USB flash drive (see instructions on how to do
70that below, in the section 'Booting the images from /binary'). 78that below, in the section 'Booting the images from /binary').