X-Git-Url: https://gerrit.automotivelinux.org/gerrit/gitweb?a=blobdiff_plain;f=README.md;h=2925e5b92fe19aca63d77148118d7191b44d9861;hb=refs%2Fchanges%2F99%2F4399%2F1;hp=4b97f74275b4d0cec81bd3e171709551439999a5;hpb=0ef8a183969cc9c3c51feb7dca5025e5773840f5;p=AGL%2Fmeta-agl-demo.git

diff --git a/README.md b/README.md
index 4b97f7427..2925e5b92 100644
--- a/README.md
+++ b/README.md
@@ -39,7 +39,7 @@ URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl
 > (or later)
 
 URI: https://github.com/meta-qt5/meta-qt5.git
-> branch:   dizzy
+> branch:   jethro (b/c of qt-5.5.x)
 > revision: adeca0db212d61a933d7952ad44ea1064cfca747
 
 ## The Renesas R-Car Gen2 (Porter) board depends in addition on: ##
@@ -72,18 +72,18 @@ These packagegroups contains packages for application framework of AGL Distro.
 Subsystem should maintain ``packagegroup-agl-appfw-[subsystem].bb`` which
 should hold sufficient packages for application framework of AGL Distro.
 
-Subsystems also can maintain thier own packagegroups under appropriate
+Subsystems also can maintain their own packagegroups under appropriate
 ``recipes-*/``.
 
 For example, Qt5 has 2 packagegroups in ``meta-agl-demo``,
-``packagegroup-agl-appfw-native-qt5`` and ``pacakgegroup-agl-demo-qt-examples``
+``packagegroup-agl-appfw-native-qt5`` and ``packagegroup-agl-demo-qt-examples``
 which are under ``recipes-qt/``.
 
 The ``packagegroup-agl-appfw-native-qt5`` is included by
-``pacakgegroup-agl-appfw-native`` because Qt5 belongs to native application
+``packagegroup-agl-appfw-native`` because Qt5 belongs to native application
 framework of AGL Distro.
 
-The ``pacakgegroup-agl-demo-qt-examples`` is added to local.conf if needed
+The ``packagegroup-agl-demo-qt-examples`` is added to local.conf if needed
 because they are not mandatory for AGL application framework and AGL Demo
 Platform.
 
@@ -151,6 +151,19 @@ You can build a QEMU image using the following steps:
 2. Build the full image of AGL Demo Platform and applications
         $ bitbake agl-demo-platform
 
+  2a. Specifically If you are building the CES2016 demos you will want to add the following to your "conf/local.conf" file to install the demo code in the image:
+IMAGE_INSTALL_append = " CES2016-demo"
+
+  2b. If you want to run QEMU directly as VM in Virtual Box or your other favorite VM software then add this line to your "conf/local.conf" file. 
+IMAGE_FSTYPES += "vmdk"
+
+  2c. The Weston IVI-Shell always gets built ; it will not be started, however, unless you specify the following in your "conf/local.conf" file :
+
+IMAGE_INSTALL_append = " \
+    weston-ivi-shell-config \
+    "
+      or you manually overwrite the "/etc/xdg/weston/weston.ini" file with a correct one.
+
 3. Run the emulator. The path for the emulator (runqemu) was added during the envsetup.
         $ cd tmp/deploy/images/qemex86-64
         $ runqemu bzImage-qemux86-64.bin agl-demo-platform-qemux86-64.ext3
@@ -159,7 +172,16 @@ You can build a QEMU image using the following steps:
         $ runqemu bzImage-qemux86-64.bin agl-demo-platform-qemux86-64.ext3 \
         bootparams="uvesafb.mode_option=1280x720-32"
 
-5. Some weston samples are available from weston terminal.
+   To extend the amount of memory, add to runqemu:
+        qemuparams="-m 512"
+
+   or use the virtual disk in Virtual Box from this location:
+	tmp/deploy/images/qemux86-64/agl-demo-platform-qemux86-64.vmdk 
+
+4. Some weston samples are available from weston terminal.
+
+
+
 
 Build a R-Car M2 (porter) image
 -------------------------------