Update README.md

Update README.md

README.md

@@ -5,9 +5,9 @@ The ROCm Platform brings a rich foundation to advanced computing by seamlessly
 #### Supported CPUs
 
 
-Starting with ROCm 1.8 we have relexed the use PCIe Atomics and also PCIe Lane choice for Vega10/GFX9 class GPU.  So now you can support CPU with out PCIe Atomics and also use Gen2 x1 lanes. 
+Starting with ROCm 1.8 we have relaxed the use of PCIe Atomics and also PCIe lane choice for Vega10/GFX9 class GPU.  So now you can support CPU without PCIe Atomics and also use Gen2 x1 lanes. 
 
-Currently our GFX8 GPU's (Fiji & Polaris Family)still need to use PCIe Gen 3 and PCIe Atomics, but are looking at relaxing this in a future release, once we have fully tested firmware. 
+Currently our GFX8 GPU's (Fiji & Polaris family) still need to use PCIe Gen 3 and PCIe Atomics, but are looking at relaxing this in a future release, once we have fully tested firmware. 
 
 
 Current CPUs which support PCIe Gen3 + PCIe Atomics are: 
@@ -18,15 +18,14 @@ Current CPUs which support PCIe Gen3 + PCIe Atomics are:
   * Intel Xeon E3 v3 or newer CPUs; 
   * Intel Core i7 v4, Core i5 v4, Core i3 v4 or newer CPUs (i.e. Haswell family or newer).
 
-For FIJI and Polaris GPU's the ROCm Platform leverages PCIe Atomics (Fetch ADD, Compare and SWAP, 
-Unconditional SWAP, AtomicsOpCompletion).
-[PCIe atomics](https://github.com/RadeonOpenCompute/RadeonOpenCompute.github.io/blob/master/ROCmPCIeFeatures.md)
-PCIe Atomics are only supported on PCIe Gen3 Enabled CPUs and PCIe Gen3 Switches like
+For Fiji and Polaris GPU's the ROCm platform leverages PCIe Atomics (Fetch and Add, Compare and Swap, 
+Unconditional Swap, AtomicsOp Completion).
+PCIe Atomics are only supported on PCIe Gen3 enabled CPUs and PCIe Gen3 switches like
 Broadcom PLX. When you install your GPUs make sure you install them in a fully
 PCIe Gen3 x16 or x8, x4 or x1  slot attached either directly to the CPU's Root I/O 
 controller or via a PCIe switch directly attached to the CPU's Root I/O 
 controller. In our experience many issues stem from trying to use consumer 
-motherboards which provide Physical x16 Connectors that are electrically 
+motherboards which provide physical x16 connectors that are electrically 
 connected as e.g. PCIe Gen2 x4 connected via the 
 Southbridge PCIe I/O controller. 
  
@@ -36,42 +35,42 @@ take advantage of PCIe Atomics. However, we still recommend that you use a CPU
 from the list provided above. 
 
 #### Not supported or very limited support under ROCm 
-###### Limited Support 
+###### Limited support 
 
 
-* With ROCm 1.8 and Vega10 it should support  PCIe Gen 2 enabled CPUs such as the AMD Opteron, Phenom, Phenom II, Athlon, Athlon X2, Athlon II and Older Intel Xeon and Intel Core Architecture and Pentium CPUs. But we have done very limited testing. Since our test farm today has been catering to CPU listed above.  This is where we need comunity support. 
- * Thunderbolt 1,2 &. 3 enabled breakout boxes GPU's should now be able to work with ROCm. Thunderbolt 1 & 2 are PCIe Gen2 based. But we have done no testing on this config and would need comunity support do limited access to this type of equipment 
+* With ROCm 1.8 and Vega10 it should support  PCIe Gen2 enabled CPUs such as the AMD Opteron, Phenom, Phenom II, Athlon, Athlon X2, Athlon II and older Intel Xeon and Intel Core Architecture and Pentium CPUs. But we have done very limited testing. Since our test farm today has been catering to CPU listed above.  This is where we need community support. 
+ * Thunderbolt 1,2 and 3 enabled breakout boxes GPU's should now be able to work with ROCm. Thunderbolt 1 and 2 are PCIe Gen2 based. But we have done no testing on this config and would need comunity support do limited access to this type of equipment 
 
-###### Not Supported 
+###### Not supported 
 
 
 * We also do not support AMD Carrizo and Kaveri APU as host for compliant dGPU attachments.
  * Thunderbolt 1 and 2 enabled GPU's are not supported by ROCm. Thunderbolt 1 & 2 are PCIe Gen2 based.
- * AMD Carrizo based APUs have limited support due to OEM & ODM's choices when it comes to some key configuration parameters. On point, we have observed that Carrizo Laptops, AIOs and Desktop systems showed inconsistencies in exposing and enabling the System BIOS parameters required by the ROCm stack. Before purchasing a Carrizo system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2. If this is the case, the final requirement is associated with correct CRAT table support - please inquire with the OEM about the latter.
- * AMD Merlin/Falcon Embedded System is also not currently supported by the public Repo.
+ * AMD Carrizo based APUs have limited support due to OEM & ODM's choices when it comes to some key configuration parameters. On point, we have observed that Carrizo laptops, AIOs and desktop systems showed inconsistencies in exposing and enabling the System BIOS parameters required by the ROCm stack. Before purchasing a Carrizo system for ROCm, please verify that the BIOS provides an option for enabling IOMMUv2. If this is the case, the final requirement is associated with correct CRAT table support - please inquire with the OEM about the latter.
+ * AMD Merlin/Falcon Embedded System is also not currently supported by the public repo.
  * AMD Raven Ridge APU are currently not supported
 
 
-### New Features to ROCm 1.8
+### New features to ROCm 1.8.1
 
 #### DKMS driver installation
 
  * Debian packages are provided for DKMS on Ubuntu
- * RPM packages are provided for CentOS/RHEL 7.4 support
+ * RPM packages are provided for CentOS/RHEL 7.4 and 7.5 support
  * See the [ROCT-Thunk-Interface](https://github.com/RadeonOpenCompute/ROCT-Thunk-Interface/tree/roc-1.8.x) and [ROCK-Kernel-Driver](https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-1.8.x) for additional documentation on driver setup
 
-#### New Distrubtuion Suppport 
+#### New distribution suppport 
 
- * Binary Package support for Ubuntu 16.04
- * Binary Package support for CentoOS 7.4
- * Binary Package support for RHEL 7.4
+ * Binary package support for Ubuntu 16.04
+ * Binary package support for CentoOS 7.4 and 7.5
+ * Binary package support for RHEL 7.4 and 7.5
  
 #### Improved OpenMPI via UCX support 
 
  * UCX support for OpenMPI
  * ROCm RDMA
 
-### The latest ROCm platform - ROCm 1.8
+### The latest ROCm platform - ROCm 1.8.1
 
 The latest tested version of the drivers, tools, libraries and source code for
 the ROCm platform have been released and are available under the roc-1.8.x or rocm-1.8.x tag
@@ -97,18 +96,18 @@ are also available on GitHub, and frozen for the rocm-1.8.0 release:
 
 #### Supported Operating Systems - New operating systems available
 
-The ROCm 1.8 platform has been tested on the following operating systems:
+The ROCm 1.8.1 platform has been tested on the following operating systems:
  * Ubuntu 16.04
  * CentOS 7.4 (Using devetoolset-7 runtime support)
  * RHEL 7.4 (Using devetoolset-7 runtime support)
 
 ### Installing from AMD ROCm repositories
 
-AMD is hosting both debian and RPM repositories for the ROCm 1.8 packages at this time.
+AMD is hosting both Debian and RPM repositories for the ROCm 1.8.1 packages at this time.
 
 The packages in the Debian repository have been signed to ensure package integrity.
 
-#### Installing from a debian repository
+#### Installing from a Debian repository
 
 ##### First make sure your system is up to date 
 
@@ -153,7 +152,7 @@ sudo apt update
 sudo apt install rocm-dkms
 ```
 
-###### Next set your permsions 
+###### Next set your permissions 
 
 With move to upstreaming the KFD driver and the support of DKMS,  for all Console aka headless user, you will need to add all  your users to the  'video" group by setting the Unix permissions
 
@@ -181,9 +180,9 @@ clinfo
 If you have an [Install Issue ](https://rocm.github.io/install_issues.html) please read this FAQ .
 
  
-###### Upon restart, To test your OpenCL instance 
+###### Upon restart, to test your OpenCL instance 
 
- Build and run Hello World OCL app..
+ Build and run Hello World OCL app.
 
 HelloWorld sample:
 
@@ -240,7 +239,7 @@ sudo apt purge $(dpkg -l | grep 'kfd\|rocm' | grep linux | grep -v libc | awk '{
 
 If possible, we would recommend starting with a fresh OS install.
 
-### CentOS/RHEL 7 Support
+### CentOS/RHEL 7 (both 7.4 and 7.5) Support
 
 Support for CentOS/RHEL 7 has been added in ROCm 1.8, but requires a special 
 runtime environment provided by the RHEL Software Collections and additional
@@ -260,7 +259,7 @@ system with the RHEL subscription server and attaching to a pool id.
 Second, enable the following repositories:
 
 ```shell
-sudo subscription-manager repos --enable rhel-7-server-rhscl-rpms
+sudo subscription-manager repos --enable rhel-server-rhscl-7-rpms
 sudo subscription-manager repos --enable rhel-7-server-optional-rpms
 sudo subscription-manager repos --enable rhel-7-server-extras-rpms
 ```
@@ -324,10 +323,10 @@ following command:
 sudo usermod -a -G video $LOGNAME 
 ```
 
-Current release supports up to CentOS/RHEL 7.4. If for any reason the system needs to be updated to 7.5, don’t update the kernel. Add “--exclude=kernel*” flag to yum install. For example:
+Current release supports up to CentOS/RHEL 7.4 and 7.5. Users should update to the latest version of the OS:
 
 ```shell
-sudo yum update --exclude=kernel*
+sudo yum update
 ```
 
 #### Compiling applications using hcc, hip, etc.
@@ -348,9 +347,9 @@ sudo yum autoremove rocm-dkms
 
 #### Known Issues / Workarounds
 
-##### If you Plan to Run with X11 - we are seeing  X freezes under load
+##### If you Plan to Run with X11 - we are seeing X freezes under load
 
-ROCm 1.8.0 a kernel parameter noretry has been set to 1 to improve overall system performance. However it has been proven to bring instability to graphics driver shipped with Ubuntu. This is an ongoing issue and we are looking into it.
+ROCm 1.8.1 a kernel parameter noretry has been set to 1 to improve overall system performance. However it has been proven to bring instability to graphics driver shipped with Ubuntu. This is an ongoing issue and we are looking into it.
 
 Before that, please try apply this change by changing noretry bit to 0.
 
@@ -368,6 +367,10 @@ Once it's done, run sudo update-initramfs -u. Reboot and verify /sys/module/amdk
 
 ##### If you are you are using hipCaffe Alexnet training on ImageNet - we are seeing sporadic hangs of hipCaffe during training
 
+##### Users without PCIe atomic support must set HSA_ENABLE_SDMA=0
+
+Some GPUs will work with ROCm if they do not support PCIe atomics. However, these cards cannot use SDMA functionality.
+
 #### Closed source components
 
 The ROCm platform relies on a few closed source components to provide legacy
@@ -400,7 +403,7 @@ Note: make sure ~/bin exists and it is part of your PATH
 
 ```shell
 mkdir ROCm && cd ROCm
-repo init -u https://github.com/RadeonOpenCompute/ROCm.git -b roc-1.8.0
+repo init -u https://github.com/RadeonOpenCompute/ROCm.git -b roc-1.8.1
 repo sync
 ```
 These series of commands will pull all of the open source code associated with

default.xml

@@ -2,11 +2,11 @@
 <manifest>
 
     <remote name="roc-github"
-            fetch="ssh://git@github.com/RadeonOpenCompute/" />
+            fetch="http://git@github.com/RadeonOpenCompute/" />
     <remote name="pctools-github"
-            fetch="ssh://git@github.com/GPUOpen-ProfessionalCompute-Tools/" />
+            fetch="http://git@github.com/GPUOpen-ProfessionalCompute-Tools/" />
 
-    <default revision="roc-1.7.x"
+    <default revision="roc-1.8.x"
              remote="roc-github"
              sync-j="4" />