rcar-gen3: README: Add Community YBSP release informationthud-Yocto-v3.15.0

This commit changes the following contents:

- Add new README (README.evaproprietary) for obtaining and installing
  the Click-through licensed Linux Drivers.
- Add Community Yocto BSP v3.15.0 release information on Yocto Project
  2.6.

Signed-off-by: Thuy Tran <thuy.tran.xh@renesas.com>
Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>

1 files changed, 140 insertions, 53 deletions

diff --git a/meta-rcar-gen3/README.md b/meta-rcar-gen3/README.md
index 83ec2be..cad7736 100644
--- a/meta-rcar-gen3/README.md
+++ b/meta-rcar-gen3/README.md
@@ -1,50 +1,97 @@
 # meta-rcar-gen3
 
-This layer provides that evaluation board is mounted ARM SoCs of Renesas
-Electronics, called the R-Car Generation 3. Currently, this supports
-board and the SoCs of the following:
-- Board: Salvator-X / SoC: R8A7795 (R-Car H3), R8A7796 (R-Car M3), R8A77965 (R-Car M3N)
-- Board: R-Car Starter Kit premier(H3ULCB) / SoC: R8A7795 (R-Car H3)
-- Board: R-Car Starter Kit pro(M3ULCB) / SoC: R8A7796 (R-Car M3)
-- Board: Ebisu / SoC: R8A77990 (R-Car E3)
 
-## Patches
+This layer provides the support for the evaluation board mounted ARM SoCs of
+Renesas Electronics, called the R-Car Generation 3.
 
-Please submit any patches for this layer to: takamitsu.honda.pv@renesas.com
-Please see the MAINTAINERS file for more details.
+Currently, this supports boards and the SoCs of the following:
+
+```bash
+    - Board: Salvator-X / SoC: R8A7795 (R-Car H3), R8A7796 (R-Car M3), R8A77965 (R-Car M3N)
+    - Board: R-Car Starter Kit premier(H3ULCB) / SoC: R8A7795 (R-Car H3)
+    - Board: R-Car Starter Kit pro(M3ULCB) / SoC: R8A7796 (R-Car M3)
+    - Board: Ebisu / SoC: R8A77990 (R-Car E3)
+```
+
+## Branch Policy
+
+
+* This is Community Yocto BSP to follow Yocto/Poky releases.
+
+* It is not supported to the level of the Customer Yocto BSP.
+
+## Tag Policy
+
+
+*  Releases are created from the respective working branch.
+
+*  After a Customer Yocto BSP version releases, the Community Yocto BSP will be
+rebased and released accordingly.
+
+*  thud-X:
+
+    * The versions used on thud (Yocto Project 2.6) will start on
+      thud-Yocto-v3.15.0 to keep the major version numbers in sync.
+
+## Contribution
+
+
+* Please submit any patches for this layer to: takamitsu.honda.pv@renesas.com
+
+* Please see the MAINTAINERS file for more details.
+
+## Layer Dependencies
 
-## Dependencies
 
 This layer depends on:
 
+* poky
+
+```bash
     URI: git://git.yoctoproject.org/poky
     layers: meta, meta-yocto, meta-yocto-bsp
-    branch: rocko
+    branch: thud
+    revision: 84eecb017ef92ef36b4df730908828e54aeff85c
+```
+* meta-linaro
 
+```bash
     URI: git://git.linaro.org/openembedded/meta-linaro.git
     layers: meta-optee
-    branch: rocko
+    branch: thud
+    revision: edb7ffc2a121df7596385595abe75180296103e0
+```
 
+* meta-openembedded
+
+```bash
     URI: git://git.openembedded.org/meta-openembedded
     layers: meta-oe
-    branch: rocko
+    branch: thud
+    revision: cca27b5ea7569d2730ee5da7ee7f47b39d775d89
+```
 
 ## Build Instructions
 
+
 The following instructions require a Poky installation (or equivalent).
 
-This also needs git user name and email defined:
+* This also needs git user name and email defined:
+
 ```bash
    $ git config --global user.email "you@example.com"
    $ git config --global user.name "Your Name"
 ```
 
-Initialize a build using the 'oe-init-build-env' script in Poky. e.g.:
+* Initialize a build using the 'oe-init-build-env' script in Poky. e.g.:
+
 ```bash
     $ source poky/oe-init-build-env
 ```
 
-After that, initialized configure bblayers.conf by adding meta-rcar-gen3 layer. e.g.:
+* After that, initialized configure bblayers.conf by adding meta-rcar-gen3 layer.
+e.g.:
+
 ```bash
     BBLAYERS ?= " \
         <path to layer>/poky/meta \
@@ -55,90 +102,130 @@ After that, initialized configure bblayers.conf by adding meta-rcar-gen3 layer.
         <path to layer>/meta-openembedded/meta-oe \
     "
 ```
-To build a specific target BSP, configure the associated machine in local.conf:
+
+* To build a specific target BSP, configure the associated machine in local.conf:
+
 ```bash
     MACHINE ??= "<supported board name>"
 ```
-Select the SOC
-```bash
-    For H3: r8a7795
-    SOC_FAMILY = "r8a7795"
 
-    For M3: r8a7796
-    SOC_FAMILY = "r8a7796"
+* Select the SOC
 
-    For M3N: r8a77965
-    SOC_FAMILY = "r8a77965"
+    * For H3: r8a7795
+
+    ```bash
+        SOC_FAMILY = "r8a7795"
+    ```
+
+    * For M3: r8a7796
+
+    ```bash
+        SOC_FAMILY = "r8a7796"
+    ```
+
+    * For M3N: r8a77965
+
+    ```bash
+        SOC_FAMILY = "r8a77965"
+    ```
+
+    * For E3: r8a77990
+
+    ```bash
+        # Already added in machine config: ebisu.conf
+        SOC_FAMILY = "r8a77990"
+    ```
+
+* Configure for systemd init in local.conf:
 
-    For E3: r8a77990
-    SOC_FAMILY = "r8a77990"
-    Already added in machine config: ebisu.conf
-```
-Configure for systemd init in local.conf:
 ```bash
     DISTRO_FEATURES_append = " systemd"
     VIRTUAL-RUNTIME_init_manager = "systemd"
 ```
-Configure for ivi-shell and ivi-extension
+
+* Configure for ivi-shell and ivi-extension
+
 ```bash
     DISTRO_FEATURES_append = " ivi-shell"
 ```
-Configure for USB 3.0
+
+* Configure for USB 3.0
+
 ```bash
     MACHINE_FEATURES_append = " usb3"
 ```
-Enable tuning support for Capacity Aware migration Strategy (CAS)
+
+* Enable tuning support for Capacity Aware migration Strategy (CAS)
+
 ```bash
     MACHINE_FEATURES_append = " cas"
 ```
-Build the target file system image using bitbake:
+
+* Build the target file system image using bitbake:
+
 ```bash
     $ bitbake core-image-minimal
 ```
-After completing the images for the target machine will be available in the output
-directory _'tmp/deploy/images/<supported board name>'_.
+
+After completing the images for the target machine will be available in the
+output directory 'tmp/deploy/images/<supported board name>'.
 
 Images generated:
+
 * Image (generic Linux Kernel binary image file)
+
 * Image-<machine name>.dtb (DTB for target machine)
+
 * core-image-minimal-<machine name>.tar.bz2 (rootfs tar+bzip2)
+
 * core-image-minimal-<machine name>.ext4  (rootfs ext4 format)
 
 ## Build Instructions for SDK
 
-This may be changed in the near feature. These instructions are tentative.
+
+NOTE:
+
+**This may be changed in the near feature. These instructions are tentative.**
 
 Should define the staticdev in SDK image feature for installing the static libs
 to SDK in local.conf.
+
 ```bash
     SDKIMAGE_FEATURES_append = " staticdev-pkgs"
 ```
-Use bitbake -c populate_sdk for generating the toolchain SDK:
-For 64-bit target SDK (aarch64):
+
+### For 64-bit target SDK (aarch64)
+
+
+Use `bitbake -c populate_sdk` for generating the toolchain SDK
+
 ```bash
     $ bitbake core-image-minimal -c populate_sdk
 ```
-The SDK can be found in the output directory _'tmp/deploy/sdk'_
 
-    poky-glibc-x86_64-core-image-minimal-aarch64-toolchain-x.x.sh
+The SDK can be found in the output directory `tmp/deploy/sdk`
+
+* `poky-glibc-x86_64-core-image-minimal-aarch64-toolchain-x.x.sh`
+
+### Usage of toolchain SDK
+
+
+Install the SDK to the default: `/opt/poky/x.x`
+
+* For 64-bit target SDK
 
-Usage of toolchain SDK: Install the SDK to the default: _/opt/poky/x.x_
-For 64-bit target SDK:
 ```bash
     $ sh poky-glibc-x86_64-core-image-minimal-aarch64-toolchain-x.x.sh
 ```
-For 64-bit application use environment script in _/opt/poky/x.x_
+
+* For 64-bit application, using environment script in `/opt/poky/x.x`
+
 ```bash
     $ source /opt/poky/x.x/environment-setup-aarch64-poky-linux
 ```
-## ULCB Information
-
-Refer to the following for more information of ULCB:
-
-    http://elinux.org/R-Car
 
-## The information on building and running Yocto on R-Car Generation 3
+## R-Car Generation 3 Information
 
-Refer to the following for more information:
 
-    https://elinux.org/R-Car/Boards/Yocto-Gen3
+Refer to the following for more information from eLinux website
+https://elinux.org/R-Car