aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorWade Farnsworth <wfarnsworth@users.noreply.github.com>2019-12-10 07:08:27 -0800
committerGitHub <noreply@github.com>2019-12-10 07:08:27 -0800
commit37a4c41fd3cb88db7a53cfa013838c3a98487fe3 (patch)
tree9f551a216b77bcd5b0e1e7088593117ae683ea4d
parent23f2ae73cc28672dbcc9ffd99fcc8d91276cdeda (diff)
parent9bf6c0562220c7aa8a3ac19c36808fd131c5cc78 (diff)
downloadmeta-amd-warrior-v1000-ga-201912.tar.gz
meta-amd-warrior-v1000-ga-201912.tar.bz2
meta-amd-warrior-v1000-ga-201912.zip
Merge pull request #668 from ArsalanHAwan/warrior-v1000-ga-201912warrior-v1000-ga-201912
release/warrior-v1000-ga-201912: add release docs and tag
-rw-r--r--BUILD.md24
-rw-r--r--CUSTOMIZE.md47
-rw-r--r--DEPLOY.md21
-rw-r--r--DOCUMENTATION.md20
-rw-r--r--FEATURES.md6
-rw-r--r--RELEASE.md40
-rw-r--r--SETUP.md27
7 files changed, 109 insertions, 76 deletions
diff --git a/BUILD.md b/BUILD.md
index a2254ea7..8fb81a02 100644
--- a/BUILD.md
+++ b/BUILD.md
@@ -1,15 +1,16 @@
# 2. Setting up and starting a build
-After [setting up the build system](SETUP.md), we can build images or
-recipes for a target machine (or BSP).
+After setting up the build system ([SETUP.md](SETUP.md)), we can build
+images or recipes for a target machine (or BSP).
Running the commands in the instructions below will setup a build for
-a selected AMD BSP, and start a build:
+a selected AMD BSP, and will start a build:
### 2.1. Select a BSP
Set the environment variable `MACHINE` to one of the
-[supported AMD BSPs](meta-amd-bsp/README.md) (change the
-`<machine-name>` in the following example accordingly):
+supported AMD BSPs (i.e. `r1000`, `v1000` or `e3000`) that you want to
+build for (change the `<machine-name>` in the following example
+accordingly):
```sh
MACHINE="<machine-name>"
```
@@ -50,15 +51,16 @@ Build one of the supported image recipes:
bitbake <image-name> -k
```
-###### where `<image-name>` is to be replaced with one of the [supported images](FEATURES.md) for the selected AMD BSP.
+###### where `<image-name>` is to be replaced with one of the supported images for the selected AMD BSP. See *supported features* section for a list all supported images for your machine.
###### (e.g. `core-image-sato` or `core-image-base`)
---
#### What's next
-Continue to "[section 3 - deploy](DEPLOY.md)" for instructions on
-booting the target with the newly built image.
+Continue to "Section 3 - Deploying an image to the target"
+([DEPLOY.md](DEPLOY.md)) for instructions on booting the target with
+the newly built image.
-You can also [customize the image](CUSTOMIZE.md) by enabling/disabling
-certain configurable features. Make sure to re-build the image before
-deploying the customized build.
+You can also customize the image ([CUSTOMIZE.md](CUSTOMIZE.md)) by
+enabling/disabling certain configurable features in the `local.conf`.
+Make sure to re-build the image before deploying the customized build.
diff --git a/CUSTOMIZE.md b/CUSTOMIZE.md
index 03031202..04cc4e38 100644
--- a/CUSTOMIZE.md
+++ b/CUSTOMIZE.md
@@ -1,4 +1,4 @@
-# Customizing images with AMD Features
+# 4. Customizing images with AMD Features
AMD supports various features and software components that can be
enabled by setting the corresponding configuration variable to a
@@ -9,37 +9,37 @@ them to be installed/available on your image, or can be configured:
* **VULKAN - Vulkan driver and Loader Layer.**
- It is required to run Vulkan based applications. Vulkan is a new
- generation graphics and compute API that provides high-efficiency,
- cross-platform access to modern GPUs.
+> It is required to run Vulkan based applications. Vulkan is a new
+> generation graphics and compute API that provides high-efficiency,
+> cross-platform access to modern GPUs.
* **MPV \* - Video player based on MPlayer/mplayer2**
- MPV is a movie player based on MPlayer and mplayer2. It supports a
- wide variety of video file formats, audio and video codecs, and
- subtitle types.
+> MPV is a movie player based on MPlayer and mplayer2. It supports a
+> wide variety of video file formats, audio and video codecs, and
+> subtitle types.
* **COMMERCIAL MULTIMEDIA \* - License restricted multimedia components**
- Certain multimedia formats require license restricted codecs and
- software components which are not included in build by default.
+> Certain multimedia formats require license restricted codecs and
+> software components which are not included in build by default.
* **MULTI DISPLAY - Multiple display support**
- You can connect multiple displays with AMD machines. The display
- configuration/arrangement can be configured using this.
+> You can connect multiple displays with AMD machines. The display
+> configuration/arrangement can be configured using this.
* **ON-TARGET DEVELOPMENT - SDK for on-target development**
- gcc, make, autotools, autoconf, build-essential etc.
+> gcc, make, autotools, autoconf, build-essential etc.
* **ON-TARGET DEBUGGING - tools for on-target debugging**
- gdb, gdbserver, strace, mtrace
+> gdb, gdbserver, strace, mtrace
* **ON-TARGET PROFILING - tools for on-target profiling**
- lttng, babeltrace, systemtap, powertop, valgrind
+> lttng, babeltrace, systemtap, powertop, valgrind
---
#### Disclaimer
@@ -66,12 +66,12 @@ target.
| Feature | Configuration variable | Configuration values | Default value | Supported BSPs |
|:----------------------|:------------------------------|:---------------------------------------|:--------------|:---------------|
-| VULKAN | INCLUDE_VULKAN | yes, no | no | r1000, v1000 |
-| MPV | INCLUDE_MPV | yes, no | no | r1000, v1000 |
-| COMMERCIAL MULTIMEDIA | INCLUDE_COMMERCIAL_MULTIMEDIA | yes, no | no | r1000, v1000 |
-| MULTI DISPLAY | MULTI_DISPLAY_MODE | auto, mirrored, extended-v, extended-h | auto | r1000, v1000 |
-| ON-TARGET DEVELOPMENT | EXTRA_IMAGE_FEATURES_append | tools-sdk | | r1000, v1000 |
-| ON-TARGET DEBUGGING | EXTRA_IMAGE_FEATURES_append | tools-debug | | r1000, v1000 |
+| VULKAN | INCLUDE_VULKAN | yes, no | no | r1000, v1000 |
+| MPV | INCLUDE_MPV | yes, no | no | r1000, v1000 |
+| COMMERCIAL MULTIMEDIA | INCLUDE_COMMERCIAL_MULTIMEDIA | yes, no | no | r1000, v1000 |
+| MULTI DISPLAY | MULTI_DISPLAY_MODE | auto, mirrored, extended-v, extended-h | auto | r1000, v1000 |
+| ON-TARGET DEVELOPMENT | EXTRA_IMAGE_FEATURES_append | tools-sdk | | r1000, v1000 |
+| ON-TARGET DEBUGGING | EXTRA_IMAGE_FEATURES_append | tools-debug | | r1000, v1000 |
| ON-TARGET PROFILING | EXTRA_IMAGE_FEATURES_append | tools-profile | | r1000, v1000 |
#### Example configuration in local.conf
@@ -90,6 +90,7 @@ EXTRA_IMAGE_FEATURES_append = " tools-profile"
---
#### What's next
-Continue to [section 2 - build](BUILD.md#23-start-the-build) and
-restart the image build as `bitbake <image-name>`, and deploy the
-new image to see the changes take effect.
+Continue to "Section 2 - Setting up and starting a build"
+([BUILD.md](BUILD.md#23-start-the-build)) and restart the image build
+as `bitbake <image-name>`, and deploy the new image to see the
+changes take effect.
diff --git a/DEPLOY.md b/DEPLOY.md
index ece6d483..7fc48159 100644
--- a/DEPLOY.md
+++ b/DEPLOY.md
@@ -1,16 +1,16 @@
# 3. Deploying an image to the target
-After [building an image](BUILD.md), we can deploy it to the target
-using a USB Flash Drive or a CD/DVD. The built images can be found in
-the `<build-dir>/tmp/deploy/images/<machine-name>` directory to
+After building an image ([BUILD.md](BUILD.md)), we can deploy it to the
+target using a USB Flash Drive or a CD/DVD. The built images can be
+found in the `<build-dir>/tmp/deploy/images/<machine-name>` directory to
which we will refer to as the **"Image Deploy Directory"** in this doc.
---
##### Note
-Change these placeholders in the following instructions according to
-the selected BSP and the image built in [section 2 - build](BUILD.md):
-* `<machine-name>`
-* `<image-name>`
+Change the `<machine-name>` and `<image-name>` placeholders in the
+following instructions according to the selected BSP and the image
+built in "Section 2 - Setting up and starting a build" ([BUILD.md](BUILD.md)).
+
---
Change directory to the Image Deploy Directory:
@@ -77,6 +77,7 @@ graphical user interface depending on the image and the target machine.
---
#### What's next
-You can also [customize the image](CUSTOMIZE.md) by enabling/disabling
-certain configurable features. Make sure to
-[re-build the image](BUILD.md) before deploying the customized build.
+You can also customize the image ([CUSTOMIZE.md](CUSTOMIZE.md)) by
+enabling/disabling certain configurable features in the `local.conf`.
+Make sure to re-build the image ([BUILD.md](BUILD.md)) before deploying
+the customized build.
diff --git a/DOCUMENTATION.md b/DOCUMENTATION.md
index 34264966..06b7211b 100644
--- a/DOCUMENTATION.md
+++ b/DOCUMENTATION.md
@@ -1,14 +1,14 @@
# Documentation
-This document lists the links to official documentation of various
+This section lists the links to official documentation of various
features and a general guide to Yocto Project and it's build system.
-| Feature | Documentation | Comments |
-|:---------------------------------------------|:--------------------------------------------------------------------------------------|:-----------------------------------------------------------------|
-| Yocto Project – Overview and Concepts Manual | https://www.yoctoproject.org/docs/2.7.1/overview-manual/overview-manual | |
-| Yocto Project – Quick Build | https://www.yoctoproject.org/docs/2.7.1/brief-yoctoprojectqs/brief-yoctoprojectqs.htm | |
-| Yocto Project – Toaster Manual | https://www.yoctoproject.org/docs/2.7.1/toaster-manual/toaster-manual.html | |
-| Yocto Project – SDK Manual | https://www.yoctoproject.org/docs/2.7.1/sdk-manual/sdk-manual.html | |
-| KGDB | https://www.kernel.org/doc/html/v4.19/dev-tools/kgdb.html | |
-| LTTng | https://lttng.org/docs/v2.10 | |
-| RGP | https://github.com/GPUOpen-Tools/Radeon-GPUProfiler/releases/tag/v1.5.1 | Follow the docs contained in the .tgz file attached on this link |
+| Feature | Documentation | Comments |
+|:---------------------------------------------|:---------------------------------------------------------------------------------------|:-----------------------------------------------------------------|
+| Yocto Project – Overview and Concepts Manual | https://www.yoctoproject.org/docs/2.7.1/overview-manual/overview-manual | |
+| Yocto Project – Quick Build | https://www.yoctoproject.org/docs/2.7.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html | |
+| Yocto Project – Toaster Manual | https://www.yoctoproject.org/docs/2.7.1/toaster-manual/toaster-manual.html | |
+| Yocto Project – SDK Manual | https://www.yoctoproject.org/docs/2.7.1/sdk-manual/sdk-manual.html | |
+| KGDB | https://www.kernel.org/doc/html/v4.19/dev-tools/kgdb.html | |
+| LTTng | https://lttng.org/docs/v2.10 | |
+| RGP | https://github.com/GPUOpen-Tools/Radeon-GPUProfiler/releases/tag/v1.5.1 | Follow the docs contained in the .tgz file attached on this link |
diff --git a/FEATURES.md b/FEATURES.md
index 721d6fff..433f547e 100644
--- a/FEATURES.md
+++ b/FEATURES.md
@@ -1,7 +1,7 @@
# Features
-This document lists the features supported for the AMD BSPs. In each
-BSP column, a "Y" represents that the feature in this row is supported
+This section lists the features supported for the AMD BSPs. In each
+BSP column, a 'Y' represents that the feature in this row is supported
for this BSP.
| Category | Feature | R1000 | V1000 |
@@ -64,7 +64,7 @@ for this BSP.
| | Touchscreen | Y | Y |
| Display Device Support | | | |
| | DP | Y | Y |
-| | HDMI | Y | |
+| | HDMI | Y | Y |
| Network Protocols | | | |
| | IPv4 | Y | Y |
| | IPv6 | Y | Y |
diff --git a/RELEASE.md b/RELEASE.md
index 4d326219..e2c39467 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -1,8 +1,8 @@
# Release notes
-This is the release notes document for the AMD BSP. This document
-contains information about the yocto layers' git repos, their branches
-and commit hashes, software versions, and known/fixed issues.
+This is the release notes document for the AMD BSP V1000. This document
+contains information about the Yocto layers' git repos, their branches
+and commit hashes, software versions, and known/fixed issues/limitations.
## Layers
| Layer | Git Repo | Branch | Commit Hash |
@@ -10,11 +10,12 @@ and commit hashes, software versions, and known/fixed issues.
| poky | git://git.yoctoproject.org/poky | warrior | 79a850a10a4b88a6d20d607b322542f947874323 |
| meta-openembedded | git://git.openembedded.org/meta-openembedded | warrior | f4ccdf2bc3fe4f00778629088baab840c868e36b |
| meta-dpdk | git://git.yoctoproject.org/meta-dpdk | warrior | c8c30c2c4e2f36b4a55a69a475fe774015423705 |
+| meta-amd | git://git.yoctoproject.org/meta-amd | warrior | tags/warrior-v1000-ga-201912 |
## Softwares
| Software | Version |
|:---------------|:-------------|
-| BIOS | RBB1201B |
+| BIOS | RBB1202B |
| linux-yocto | 4.19.8 |
| gcc | 8.3.0 |
| util-linux | 2.32.1 |
@@ -39,9 +40,32 @@ and commit hashes, software versions, and known/fixed issues.
| rgp | 1.5.1 |
## Fixed Issues
-| None |
-|:-----|
+| # V1000 Fixed Issues # |
+|:------------------------------------------------------------------------------------|
+| Hard hang with mpv vaapi-vappi configuration in fullscreen mode on V1000 |
+| Stutter observed with 4k@60 video playback on V1000 |
+| Display goes blank after hotplug of third monitor on V1000 |
+| Glmark2 overnight hang |
+| I2S Audio one side of headset is not audible while playing i2S audio on V1000/R1000 |
## Known Issues
-| None |
-|:-----|
+| # V1000 Known Issues/Limitations # |
+|:----------------------------------------------------------------------------------------------------------------------|
+| Stuttering is observed with vulkan hologram sample on 4k monitor full screen mode |
+| S3 fails at 25th cycle on Dibbler V1000 due to PSP bug |
+| Display artifacts while doing S3 with max 4k monitors on APU’s |
+| __* XGBE__ |
+| SFP wont work on V1807 platforms after few hours |
+| Ethernet link is showing always up on RJ45 ports of Bilby platforms |
+| _** Workaround: Disable the port which is not connected the ethernet cable_ |
+| Hotplug failures and stability issue with longer duration performance test on Bilby platforms with RJ45 ports enabled |
+| _** Workaround: Disable the port which is not connected the ethernet cable_ |
+| Can’t concurrently enable SFP+ and RJ45 interfaces |
+| Peer to Peer network is unstable with 1/10G SFP (FC) |
+| No IEEE 1588 Timestamp support |
+| No receive split header support |
+| __* Following features should be functional but have not been fully validated:__ |
+| *** Priority and VLAN (VLAN Priority Control) |
+| *** RMON Counter |
+| *** VLAN support and Receive-Side scaling |
+| *** 2.5G TCP/IP offload (duplex) and 2.5G jumbo frames (duplex) |
diff --git a/SETUP.md b/SETUP.md
index 65d466b1..258157ae 100644
--- a/SETUP.md
+++ b/SETUP.md
@@ -3,17 +3,17 @@
Building images for AMD BSPs requires setting up the Yocto Project
Build System. Please follow the guidelines on
[Yocto Project Overview and Concepts Manual](https://www.yoctoproject.org/docs/2.7.1/overview-manual/overview-manual.html)
-and [Yocto Project Quick Build](https://www.yoctoproject.org/docs/2.7.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html)
+and [Yocto Project Quick Build Guide](https://www.yoctoproject.org/docs/2.7.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html)
if you are not familiar with the Yocto Project and it's Build System.
Running the following commands will setup the build system and will
enable us to build recipes & images for any of the
-[supported AMD BSPs](meta-amd-bsp/README.md).
+supported AMD BSPs (i.e `r1000`, `v1000` or `e3000`).
### 1.1 Prerequisites
-Install the build system's dependencies
-```
+Install the build system's dependencies:
+```sh
sudo apt install -y gawk wget git-core diffstat unzip texinfo \
gcc-multilib build-essential chrpath socat cpio python python3 \
python3-pip python3-pexpect xz-utils debianutils iputils-ping \
@@ -29,11 +29,15 @@ YOCTO_BRANCH="warrior"
Clone the git repositories:
```sh
-git clone --single-branch --branch "${YOCTO_BRANCH}" "git://git.yoctoproject.org/poky" "poky-amd"
+git clone --single-branch --branch "${YOCTO_BRANCH}" \
+ "git://git.yoctoproject.org/poky" "poky-amd"
cd poky-amd
-git clone --single-branch --branch "${YOCTO_BRANCH}" "git://git.openembedded.org/meta-openembedded"
-git clone --single-branch --branch "${YOCTO_BRANCH}" "git://git.yoctoproject.org/meta-dpdk"
-git clone --single-branch --branch "${YOCTO_BRANCH}" "git://git.yoctoproject.org/meta-amd"
+git clone --single-branch --branch "${YOCTO_BRANCH}" \
+ "git://git.openembedded.org/meta-openembedded"
+git clone --single-branch --branch "${YOCTO_BRANCH}" \
+ "git://git.yoctoproject.org/meta-dpdk"
+git clone --single-branch --branch "${YOCTO_BRANCH}" \
+ "git://git.yoctoproject.org/meta-amd"
```
Checkout commit hashes:
@@ -44,12 +48,13 @@ git checkout --quiet f4ccdf2bc3fe4f00778629088baab840c868e36b
cd ../meta-dpdk
git checkout --quiet c8c30c2c4e2f36b4a55a69a475fe774015423705
cd ../meta-amd
-git checkout --quiet HEAD
+git checkout --quiet tags/warrior-v1000-ga-201912
cd ..
```
---
#### What's next
-Continue to "[section 2 - build](BUILD.md)" for instructions on how to
-setup and start a build for a particular AMD BSP.
+Continue to "Section 2 - Setting up and starting a build"
+([BUILD.md](BUILD.md)) for instructions on how to setup and start a
+build for a particular AMD BSP.