summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLeon Anavi <leon.anavi@konsulko.com>2017-03-06 11:24:07 +0200
committerLeon Anavi <leon.anavi@konsulko.com>2017-03-06 11:24:07 +0200
commit2daf41e5fc8e2971215ccdaa49efdc7ecdc0b930 (patch)
tree875aa194109c8c6aea118b1730d9d8a45ba9e5bb
parent9e314198e85becc8fd11bdfdb784a79081851469 (diff)
docs/getting-started: Fix format
Fix format to ensure that pandoc will generate successfully HTML, PDF and docuwiki documents. The docuwiki output has been used to update the articles in the AGL wiki. Bug-AGL: SPEC-461 Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
-rw-r--r--getting-started/source-code.md4
-rw-r--r--getting-started/troubleshooting.md19
2 files changed, 18 insertions, 5 deletions
diff --git a/getting-started/source-code.md b/getting-started/source-code.md
index 0e878d3..45899cc 100644
--- a/getting-started/source-code.md
+++ b/getting-started/source-code.md
@@ -1,7 +1,9 @@
# Introduction: Building target AGL image with Yocto project
+
The standard Yocto process is made of the following steps:
+
* Setting up your operating system.
* Setting up the build environment for R-Car BSP.
* Downloading the proprietary drivers and installing them in the build environment (if needed).
@@ -20,6 +22,7 @@ If you want to bypass the build phase and quick boot the board, you can download
The very first step is to ensure that your system can run the build system of the Yocto Project.
**Important**: it only runs on Linux
+
* if your system is Windows© or iOS© you should use a virtualization solution (Virtualbox, VMWare ...) to run a Linux VM on your system.
For AGL 2.1, Yocto Project 2.1, known as krogoth, has been selected for the BSP and build system.
@@ -29,6 +32,7 @@ Reference data for configuring your system can be found in the Yocto documentati
Here after an extract of this documentation for most common Linux distributions:
+
* The build system should be able to run on any modern distributions that has the following versions for:
* Python
* Git 1.7.8 or greater
diff --git a/getting-started/troubleshooting.md b/getting-started/troubleshooting.md
index e252640..0027738 100644
--- a/getting-started/troubleshooting.md
+++ b/getting-started/troubleshooting.md
@@ -2,7 +2,7 @@
## Extended attributes MUST be copied
-***IMPORTANT, The extended attribute set during image construction MUST be copied to the SD card.***
+**IMPORTANT, The extended attribute set during image construction MUST be copied to the SD card.**
When using tar to create the SDcard, it is a common error to not copy the extended attributes. Find below instruction for using tar.
@@ -49,22 +49,31 @@ TARGET_CXXFLAGS_remove_pn-gcc-runtime = "-D_GLIBCXX_USE_CXX11_ABI=0" CXXFLAGS_re
To disable IVI-Shell and revert to the "plain old" weston desktop, you can follow the 4 steps below:
-1. modify */etc/xdg/weston/weston.ini* and comment the line mentioning IVI-shell. For example on Porter board:
+* Modify */etc/xdg/weston/weston.ini* and comment the line mentioning IVI-shell. For example on Porter board:
+```
[core]
backend=drm-backend.so
#shell=ivi-shell.so
...
-2. modify */usr/lib/systemd/user/afm-user-daemon.service* and comment the line specifying QT Wayland backend:
+```
+
+* modify */usr/lib/systemd/user/afm-user-daemon.service* and comment the line specifying QT Wayland backend:
+```
...
#Environment=QT_WAYLAND_SHELL_INTEGRATION=ivi-shell
...
-3. disable Homescreen services:
+```
+* disable Homescreen services:
+
+```
# systemctl disable HomeScreenAppFrameworkBinderAGL.service
# systemctl disable HomeScreen.service
# systemctl disable InputEventManager.service
# systemctl disable WindowManager.service
-4. Reboot your target and you should then be able to start apps on the standard weston screen using afm-util
+```
+
+* Reboot your target and you should then be able to start apps on the standard weston screen using afm-util