Change extraction protocol to http.

Change-Id: I901192123c7876c6ca1a40e90c72415488252e88

.github/CODEOWNERS

@@ -1 +0,0 @@
-* @saadrahim @Rmalavally @amd-aakash @zhang2amd @jlgreathouse @samjwu @MathiasMagnus

.github/dependabot.yml

@@ -1,12 +0,0 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for all configuration options:
-# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
-
-version: 2
-updates:
-  - package-ecosystem: "pip" # See documentation for possible values
-    directory: "/docs/sphinx" # Location of package manifests
-    open-pull-requests-limit: 10
-    schedule:
-      interval: "daily"

.github/workflows/linting.yml

@@ -1,60 +0,0 @@
-name: Linting
-
-on:
-  push:
-    branches: 
-    - develop
-    - main
-    - 'docs/*'
-    - 'roc**'    
-  pull_request:
-    branches: 
-    - develop
-    - main
-    - 'docs/*'
-    - 'roc**'
-
-concurrency:
-  group: ${{ github.ref }}-${{ github.workflow }}
-  cancel-in-progress: true
-
-jobs:
-  lint-rest:
-    name: "RestructuredText"
-    runs-on: ubuntu-latest
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v3
-    - name: Install rst-lint
-      run: pip install restructuredtext-lint
-    - name: Lint ResT files
-      run: rst-lint ${{ join(github.workspace, '/docs') }}
-
-  lint-md:
-    name: "Markdown"
-    runs-on: ubuntu-latest
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v3
-    - name: Use markdownlint-cli2
-      uses: DavidAnson/markdownlint-cli2-action@v10.0.1
-      with:
-        globs: '**/*.md'
-
-  spelling:
-    name: "Spelling"
-    runs-on: ubuntu-latest
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v3
-    - name: Fetch config
-      shell: sh
-      run: |
-        curl --silent --show-error --fail --location https://raw.github.com/RadeonOpenCompute/rocm-docs-core/develop/.spellcheck.yaml -O
-        curl --silent --show-error --fail --location https://raw.github.com/RadeonOpenCompute/rocm-docs-core/develop/.wordlist.txt >> .wordlist.txt
-    - name: Run spellcheck
-      uses: rojopolis/spellcheck-github-actions@0.30.0
-    - name: On fail
-      if: failure()
-      run: |
-        echo "Please check for spelling mistakes or add them to '.wordlist.txt' in either the root of this project or in rocm-docs-core."

.gitignore

@@ -1,18 +0,0 @@
-.venv
-.vscode
-build
-
-# documentation artifacts
-_build/
-_images/
-_static/
-_templates/
-_toc.yml
-docBin/
-_doxygen/
-_readthedocs/
-
-# avoid duplicating contributing.md due to conf.py
-docs/contributing.md
-docs/release.md
-docs/CHANGELOG.md

.markdownlint-cli2.yaml

@@ -1,14 +0,0 @@
-config:
-  default: true
-  MD013: false
-  MD026:
-    punctuation: '.,;:!'
-  MD029:
-    style: ordered
-  MD033: false
-  MD034: false
-  MD041: false
-ignores:
-  - CHANGELOG.md
-  - "{,docs/}{RELEASE,release}.md"
-  - tools/autotag/templates/**/*.md

.readthedocs.yaml

@@ -1,21 +0,0 @@
-# Read the Docs configuration file
-# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
-
-version: 2
-
-build:
-   os: ubuntu-22.04
-   tools:
-      python: "3.10"
-   apt_packages:
-     - "doxygen"
-     - "graphviz" # For dot graphs in doxygen
-
-python:
-   install:
-   - requirements: docs/sphinx/requirements.txt
-
-sphinx:
-   configuration: docs/conf.py
-
-formats: []

.wordlist.txt

@@ -1,686 +0,0 @@
-AAC
-ABI
-ACE
-ACEs
-AccVGPR
-AccVGPRs
-ALU
-AMD
-AMDGPU
-AMDGPUs
-AMDMIGraphX
-AMI
-AOCC
-AOMP
-APIC
-APIs
-APU
-ASIC
-ASICs
-ASan
-ASm
-ATI
-AddressSanitizer
-AlexNet
-Arb
-BLAS
-BMC
-BitCode
-Blit
-Bluefield
-CCD
-CDNA
-CIFAR
-CLI
-CLion
-CMake
-CMakeLists
-CMakePackage
-CP
-CPC
-CPF
-CPP
-CPU
-CPUs
-CSC
-CSE
-CSV
-CSn
-CTests
-CU
-CUDA
-CUs
-CXX
-Cavium
-CentOS
-ChatGPT
-CoRR
-Codespaces
-Commitizen
-CommonMark
-Concretized
-Conda
-ConnectX
-DGEMM
-DKMS
-DL
-DMA
-DNN
-DNNL
-DPM
-DRI
-DW
-DWORD
-Dask
-DataFrame
-DataLoader
-DataParallel
-DeepSpeed
-Dependabot
-DevCap
-Dockerfile
-Doxygen
-ELMo
-ENDPGM
-EPYC
-ESXi
-FFT
-FFTs
-FFmpeg
-FHS
-FMA
-FP
-Filesystem
-Flang
-Fortran
-Fuyu
-GALB
-GCD
-GCDs
-GCN
-GDB
-GDDR
-GDR
-GDS
-GEMM
-GEMMs
-GFortran
-GiB
-GIM
-GL
-GLXT
-GMI
-GPG
-GPR
-GPT
-GPU
-GPU's
-GPUs
-GRBM
-GenAI
-GenZ
-GitHub
-Gitpod
-HBM
-HCA
-HIPCC
-HIPExtension
-HIPIFY
-HPC
-HPCG
-HPE
-HPL
-HSA
-HWE
-Haswell
-Higgs
-Hyperparameters
-ICV
-IDE
-IDEs
-IMDb
-IOMMU
-IOP
-IOPM
-IOV
-IRQ
-ISA
-ISV
-ISVs
-ImageNet
-InfiniBand
-Inlines
-IntelliSense
-Intersphinx
-Intra
-Ioffe
-JSON
-Jupyter
-KFD
-KiB
-KVM
-Keras
-Khronos
-LAPACK
-LCLK
-LDS
-LLM
-LLMs
-LLVM
-LM
-LSAN
-LTS
-LoRA
-MEM
-MERCHANTABILITY
-MFMA
-MiB
-MIGraphX
-MIOpen
-MIOpenGEMM
-MIVisionX
-MLM
-MMA
-MMIO
-MMIOH
-MNIST
-MPI
-MSVC
-MVAPICH
-MVFFR
-Makefile
-Makefiles
-Matplotlib
-Megatron
-Mellanox
-Mellanox's
-Meta's
-MirroredStrategy
-Multicore
-Multithreaded
-MyEnvironment
-MyST
-NBIO
-NBIOs
-NIC
-NICs
-NLI
-NLP
-NPS
-NSP
-NUMA
-NVCC
-NVIDIA
-NVPTX
-NaN
-Nano
-Navi
-Noncoherently
-NousResearch's
-NumPy
-OAM
-OAMs
-OCP
-OEM
-OFED
-OMP
-OMPI
-OMPT
-OMPX
-ONNX
-OSS
-OSU
-OpenCL
-OpenCV
-OpenFabrics
-OpenGL
-OpenMP
-OpenSSL
-OpenVX
-PCI
-PCIe
-PEFT
-PIL
-PILImage
-PRNG
-PRs
-PaLM
-Pageable
-PeerDirect
-Perfetto
-PipelineParallel
-PnP
-PowerShell
-PyPi
-PyTorch
-Qcycles
-RAII
-RCCL
-RDC
-RDMA
-RDNA
-RHEL
-ROC
-ROCProfiler
-ROCTracer
-ROCclr
-ROCdbgapi
-ROCgdb
-ROCk
-ROCm
-ROCmCC
-ROCmSoftwarePlatform
-ROCmValidationSuite
-ROCr
-RST
-RW
-Radeon
-RelWithDebInfo
-Req
-Rickle
-RoCE
-Ryzen
-SALU
-SBIOS
-SCA
-SDK
-SDMA
-SDRAM
-SENDMSG
-SGPR
-SGPRs
-SHA
-SIGQUIT
-SIMD
-SIMDs
-SKU
-SKUs
-SLES
-SMEM
-SMI
-SMT
-SPI
-SQs
-SRAM
-SRAMECC
-SVD
-SWE
-SerDes
-Shlens
-Skylake
-Softmax
-Spack
-Supermicro
-Szegedy
-TCA
-TCC
-TCI
-TCIU
-TCP
-TCR
-TF
-TFLOPS
-TPU
-TPUs
-TensorBoard
-TensorFlow
-TensorParallel
-ToC
-TorchAudio
-TorchMIGraphX
-TorchScript
-TorchServe
-TorchVision
-TransferBench
-TrapStatus
-UAC
-UC
-UCC
-UCX
-UIF
-USM
-UTCL
-UTIL
-Uncached
-Unhandled
-VALU
-VBIOS
-VGPR
-VGPRs
-VM
-VMEM
-VMWare
-VRAM
-VSIX
-VSkipped
-Vanhoucke
-Vulkan
-WGP
-WGPs
-WX
-WikiText
-Wojna
-Workgroups
-Writebacks
-XCD
-XCDs
-XGBoost
-XGBoost's
-XGMI
-XT
-XTX
-Xeon
-Xilinx
-Xnack
-Xteam
-YAML
-YML
-YModel
-ZeRO
-ZenDNN
-accuracies
-activations
-addr
-alloc
-allocator
-allocators
-amdgpu
-api
-atmi
-atomics
-autogenerated
-avx
-awk
-backend
-backends
-benchmarking
-bfloat
-bilinear
-bitsandbytes
-blit
-boson
-bosons
-buildable
-bursty
-bzip
-cacheable
-cd
-centos
-centric
-changelog
-chiplet
-cmake
-cmd
-coalescable
-codename
-collater
-comgr
-completers
-composable
-concretization
-config
-conformant
-convolutional
-convolves
-cpp
-csn
-cuBLAS
-cuFFT
-cuLIB
-cuRAND
-cuSOLVER
-cuSPARSE
-dataset
-datasets
-dataspace
-datatype
-datatypes
-dbgapi
-de
-deallocation
-denoise
-denoised
-denoises
-denormalize
-deserializers
-detections
-dev
-devicelibs
-devsel
-dimensionality
-disambiguates
-distro
-el
-embeddings
-enablement
-endpgm
-encodings
-env
-epilog
-etcetera
-ethernet
-exascale
-executables
-ffmpeg
-filesystem
-fortran
-galb
-gcc
-gdb
-gfortran
-gfx
-githooks
-github
-gnupg
-grayscale
-gzip
-heterogenous
-hipBLAS
-hipBLASLt
-hipCUB
-hipFFT
-hipLIB
-hipRAND
-hipSOLVER
-hipSPARSE
-hipSPARSELt
-hipTensor
-hipamd
-hipblas
-hipcub
-hipfft
-hipfort
-hipify
-hipsolver
-hipsparse
-hpp
-hsa
-hsakmt
-hyperparameter
-ib_core
-inband
-incrementing
-inferencing
-inflight
-init
-initializer
-inlining
-installable
-interprocedural
-intra
-invariants
-invocating
-ipo
-kdb
-latencies
-libfabric
-libjpeg
-libs
-linearized
-linter
-linux
-llvm
-localscratch
-logits
-lossy
-macOS
-matchers
-microarchitecture
-migraphx
-miopen
-miopengemm
-mivisionx
-mkdir
-mlirmiopen
-mtypes
-mvffr
-namespace
-namespaces
-numref
-ocl
-opencl
-opencv
-openmp
-openssl
-optimizers
-os
-pageable
-parallelization
-parameterization
-passthrough
-perfcounter
-performant
-perl
-pragma
-pre
-prebuilt
-precompiled
-prefetch
-prefetchable
-preprocess
-preprocessed
-preprocessing
-prequantized
-prerequisites
-profiler
-protobuf
-pseudorandom
-py
-quasirandom
-queueing
-rccl
-rdc
-reStructuredText
-reformats
-repos
-representativeness
-req
-resampling
-rescaling
-reusability
-roadmap
-roc
-rocAL
-rocALUTION
-rocBLAS
-rocFFT
-rocLIB
-rocMLIR
-rocPRIM
-rocRAND
-rocSOLVER
-rocSPARSE
-rocThrust
-rocWMMA
-rocalution
-rocblas
-rocclr
-rocfft
-rocm
-rocminfo
-rocprim
-rocprof
-rocprofiler
-rocr
-rocrand
-rocsolver
-rocsparse
-rocthrust
-roctracer
-runtime
-runtimes
-sL
-scalability
-scalable
-sendmsg
-serializers
-shader
-sharding
-sigmoid
-sm
-smi
-softmax
-spack
-src
-stochastically
-strided
-subdirectory
-subexpression
-subfolder
-subfolders
-supercomputing
-tensorfloat
-th
-tokenization
-tokenize
-tokenized
-tokenizer
-tokenizes
-toolchain
-toolchains
-toolset
-toolsets
-torchvision
-tqdm
-tracebacks
-txt
-uarch
-uncached
-uncorrectable
-uninstallation
-unsqueeze
-unstacking
-unswitching
-untrusted
-untuned
-upvote
-USM
-UTCL
-UTIL
-utils
-vL
-variational
-vdi
-vectorizable
-vectorization
-vectorize
-vectorized
-vectorizer
-vectorizes
-vjxb
-walkthrough
-walkthroughs
-wavefront
-wavefronts
-whitespaces
-workgroup
-workgroups
-writeback
-writebacks
-wrreq
-wzo
-xargs
-xz
-yaml
-ysvmadyb
-zypper

CONTRIBUTING.md

@@ -1,246 +0,0 @@
-# Contributing to ROCm Docs
-
-AMD values and encourages the ROCm community to contribute to our code and
-documentation. This repository is focused on ROCm documentation and this
-contribution guide describes the recommend method for creating and modifying our
-documentation.
-
-While interacting with ROCm Documentation, we encourage you to be polite and
-respectful in your contributions, content or otherwise. Authors, maintainers of
-these docs act on good intentions and to the best of their knowledge.
-Keep that in mind while you engage. Should you have issues with contributing
-itself, refer to
-[discussions](https://github.com/RadeonOpenCompute/ROCm/discussions) on the
-GitHub repository.
-
-## Supported Formats
-
-Our documentation includes both markdown and rst files. Markdown is encouraged
-over rst due to the lower barrier to participation. GitHub flavored markdown is preferred
-for all submissions as it will render accurately on our GitHub repositories. For existing documentation,
-[MyST](https://myst-parser.readthedocs.io/en/latest/intro.html) markdown
-is used to implement certain features unsupported in GitHub markdown. This is
-not encouraged for new documentation. AMD will transition
-to stricter use of GitHub flavored markdown with a few caveats. ROCm documentation
-also uses [sphinx-design](https://sphinx-design.readthedocs.io/en/latest/index.html)
-in our markdown and rst files. We also will use breathe syntax for doxygen documentation
-in our markdown files. Other design elements for effective HTML rendering of the documents
-may be added to our markdown files. Please see
-[GitHub](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github)'s
-guide on writing and formatting on GitHub as a starting point.
-
-ROCm documentation adds additional requirements to markdown and rst based files
-as follows:
-
-- Level one headers are only used for page titles. There must be only one level
-  1 header per file for both Markdown and Restructured Text.
-- Pass [markdownlint](https://github.com/markdownlint/markdownlint) check via
-  our automated github action on a Pull Request (PR).
-
-## Filenames and folder structure
-
-Please use snake case for file names. Our documentation follows pitchfork for
-folder structure. All documentation is in /docs except for special files like
-the contributing guide in the / folder. All images used in the documentation are
-place in the /docs/data folder.
-
-## How to provide feedback for for ROCm documentation
-
-There are three standard ways to provide feedback for this repository.
-
-### Pull Request
-
-All contributions to ROCm documentation should arrive via the
-[GitHub Flow](https://docs.github.com/en/get-started/quickstart/github-flow)
-targetting the develop branch of the repository. If you are unable to contribute
-via the GitHub Flow, feel free to email us. TODO, confirm email address.
-
-### GitHub Issue
-
-Issues on existing or absent docs can be filed as [GitHub issues
-](https://github.com/RadeonOpenCompute/ROCm/issues).
-
-### Email Feedback
-
-## Language and Style
-
-Adopting Microsoft CPP-Docs guidelines for [Voice and Tone
-](https://github.com/MicrosoftDocs/cpp-docs/blob/main/styleguide/voice-tone.md).
-
-ROCm documentation templates to be made public shortly. ROCm templates dictate
-the recommended structure and flow of the documentation. Guidelines on how to
-integrate figures, equations, and tables are all based off
-[MyST](https://myst-parser.readthedocs.io/en/latest/intro.html).
-
-Font size and selection, page layout, white space control, and other formatting
-details are controlled via rocm-docs-core, sphinx extention. Please raise issues
-in rocm-docs-core for any formatting concerns and changes requested.
-
-## Building Documentation
-
-While contributing, one may build the documentation locally on the command-line
-or rely on Continuous Integration for previewing the resulting HTML pages in a
-browser.
-
-### Command line documentation builds
-
-Python versions known to build documentation:
-
-- 3.8
-
-To build the docs locally using Python Virtual Environment (`venv`), execute the
-following commands from the project root:
-
-```sh
-python3 -mvenv .venv
-# Windows
-.venv/Scripts/python -m pip install -r docs/sphinx/requirements.txt
-.venv/Scripts/python -m sphinx -T -E -b html -d _build/doctrees -D language=en docs _build/html
-# Linux
-.venv/bin/python     -m pip install -r docs/sphinx/requirements.txt
-.venv/bin/python     -m sphinx -T -E -b html -d _build/doctrees -D language=en docs _build/html
-```
-
-Then open up `_build/html/index.html` in your favorite browser.
-
-### Pull Requests documentation builds
-
-When opening a PR to the `develop` branch on GitHub, the page corresponding to
-the PR (`https://github.com/RadeonOpenCompute/ROCm/pull/<pr_number>`) will have
-a summary at the bottom. This requires the user be logged in to GitHub.
-
-- There, click `Show all checks` and `Details` of the Read the Docs pipeline. It
-  will take you to `https://readthedocs.com/projects/advanced-micro-devices-rocm/
-  builds/<some_build_num>/`
-  - The list of commands shown are the exact ones used by CI to produce a render
-    of the documentation.
-- There, click on the small blue link `View docs` (which is not the same as the
-  bigger button with the same text). It will take you to the built HTML site with
-  a URL of the form `https://
-  advanced-micro-devices-demo--<pr_number>.com.readthedocs.build/projects/alpha/en
-  /<pr_number>/`.
-
-### Build the docs using VS Code
-
-One can put together a productive environment to author documentation and also
-test it locally using VS Code with only a handful of extensions. Even though the
-extension landscape of VS Code is ever changing, here is one example setup that
-proved useful at the time of writing. In it, one can change/add content, build a
-new version of the docs using a single VS Code Task (or hotkey), see all errors/
-warnings emitted by Sphinx in the Problems pane and immediately see the
-resulting website show up on a locally serving web server.
-
-#### Configuring VS Code
-
-1. Install the following extensions:
-
-    - Python (ms-python.python)
-    - Live Server (ritwickdey.LiveServer)
-
-2. Add the following entries in `.vscode/settings.json`
-
-    ```json
-    {
-      "liveServer.settings.root": "/.vscode/build/html",
-      "liveServer.settings.wait": 1000,
-      "python.terminal.activateEnvInCurrentTerminal": true
-    }
-    ```
-
-    The settings in order are set for the following reasons:
-    - Sets the root of the output website for live previews. Must be changed
-      alongside the `tasks.json` command.
-    - Tells live server to wait with the update to give time for Sphinx to
-      regenerate site contents and not refresh before all is don. (Empirical value)
-    - Automatic virtual env activation is a nice touch, should you want to build
-      the site from the integrated terminal.
-
-3. Add the following tasks in `.vscode/tasks.json`
-
-    ```json
-    {
-      "version": "2.0.0",
-      "tasks": [
-        {
-          "label": "Build Docs",
-          "type": "process",
-          "windows": {
-            "command": "${workspaceFolder}/.venv/Scripts/python.exe"
-          },
-          "command": "${workspaceFolder}/.venv/bin/python3",
-          "args": [
-            "-m",
-            "sphinx",
-            "-j",
-            "auto",
-            "-T",
-            "-b",
-            "html",
-            "-d",
-            "${workspaceFolder}/.vscode/build/doctrees",
-            "-D",
-            "language=en",
-            "${workspaceFolder}/docs",
-            "${workspaceFolder}/.vscode/build/html"
-          ],
-          "problemMatcher": [
-            {
-              "owner": "sphinx",
-              "fileLocation": "absolute",
-              "pattern": {
-                "regexp": "^(?:.*\\.{3}\\s+)?(\\/[^:]*|[a-zA-Z]:\\\\[^:]*):(\\d+):\\s+(WARNING|ERROR):\\s+(.*)$",
-                "file": 1,
-                "line": 2,
-                "severity": 3,
-                "message": 4
-              },
-            },
-            {
-              "owner": "sphinx",
-              "fileLocation": "absolute",
-              "pattern": {
-                "regexp": "^(?:.*\\.{3}\\s+)?(\\/[^:]*|[a-zA-Z]:\\\\[^:]*):{1,2}\\s+(WARNING|ERROR):\\s+(.*)$",
-                "file": 1,
-                "severity": 2,
-                "message": 3
-              }
-            }
-          ],
-          "group": {
-            "kind": "build",
-            "isDefault": true
-          }
-        },
-      ],
-    }
-    ```
-
-    > (Implementation detail: two problem matchers were needed to be defined,
-    > because VS Code doesn't tolerate some problem information being potentially
-    > absent. While a single regex could match all types of errors, if a capture
-    > group remains empty (the line number doesn't show up in all warning/error
-    > messages) but the `pattern` references said empty capture group, VS Code
-    > discards the message completely.)
-
-4. Configure Python virtual environment (venv)
-
-    - From the Command Palette, run `Python: Create Environment`
-      - Select `venv` environment and the `docs/sphinx/requirements.txt` file.
-      _(Simply pressing enter while hovering over the file from the dropdown is
-      insufficient, one has to select the radio button with the 'Space' key if
-      using the keyboard.)_
-
-5. Build the docs
-
-    - Launch the default build Task using either:
-      - a hotkey _(default is 'Ctrl+Shift+B')_ or
-      - by issuing the `Tasks: Run Build Task` from the Command Palette.
-
-6. Open the live preview
-
-    - Navigate to the output of the site within VS Code, right-click on
-    `.vscode/build/html/index.html` and select `Open with Live Server`. The
-    contents should update on every rebuild without having to refresh the
-    browser.
-
-<!-- markdownlint-restore -->

LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2023 Advanced Micro Devices, Inc. All rights reserved.
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

README.md

@@ -1,54 +1,57 @@
-# AMD ROCm™ Platform
+## Are You Ready to ROCK?
+The ROCm Platform bringing a rich foundation to advanced computing by better
+integrating the CPU and GPU to solve real-world problems.
 
-ROCm™ is an open-source stack for GPU computation. ROCm is primarily Open-Source
-Software (OSS) that allows developers the freedom to customize and tailor their
-GPU software for their own needs while collaborating with a community of other
-developers, and helping each other find solutions in an agile, flexible, rapid
-and secure manner.
+On April 25th, 2016, we delivered ROCm 1.0 built around three core foundation
+elements:
 
-ROCm is a collection of drivers, development tools and APIs enabling GPU
-programming from the low-level kernel to end-user applications. ROCm is powered
-by AMD’s Heterogeneous-computing Interface for Portability (HIP), an OSS C++ GPU
-programming environment and its corresponding runtime. HIP allows ROCm
-developers to create portable applications on different platforms by deploying
-code on a range of platforms, from dedicated gaming GPUs to exascale HPC
-clusters. ROCm supports programming models such as OpenMP and OpenCL, and
-includes all the necessary OSS compilers, debuggers and libraries. ROCm is fully
-integrated into ML frameworks such as PyTorch and TensorFlow. ROCm can be
-deployed in many ways, including through the use of containers such as Docker,
-Spack, and your own build from source.
+Open Hetrogenous Computing Platform (Linux(R) Driver and Runtime Stack)
+optimized for HPC & Ultra-scale class computing Heterogeneous C and C++
+Single Source to better address the whole system computation not just a GPU
+device HIP acknowledging the need for platform choice when utilizing GPU
+computing API
 
-ROCm’s goal is to allow our users to maximize their GPU hardware investment.
-ROCm is designed to help develop, test and deploy GPU accelerated HPC, AI,
-scientific computing, CAD, and other applications in a free, open-source,
-integrated and secure software ecosystem.
+Using our knowledge of the HSA Standards and, more importantly, the HSA
+Runtime we have been able to successfully extended support to the dGPU with
+critical features for NUMA class acceleration. As a result, the ROCK driver is
+composed of several components based on our efforts to develop the
+Heterogeneous System Architecture for APUs, including the new AMDGPU driver,
+the Kernel Fusion Driver (KFD), the HSA+ Runtime and an LLVM based compilation
+stack for the building of key language support. This support starts with AMD’s
+Fiji Family of dGPU, and has expanded to include the Hawaii dGPU Family in
+ROCm 1.2.
 
-This repository contains the manifest file for ROCm™ releases, changelogs, and
-release information. The file default.xml contains information for all
-repositories and the associated commit used to build the current ROCm release.
+### Overview and Installation Instructions
+For an overview of the ROCm stack, installation instructions, and other supporting
+documentation, please refer to https://radeonopencompute.github.io
 
-The default.xml file uses the repo Manifest format.
+### The Latest ROCm Platform - ROCm 1.3
+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.3.0 tag.
+The repo tool can be used to checkout the full software stack.
 
-The develop branch of this repository contains content for the next
-ROCm release.
+#### Installing repo
+Google's repo tool allows you to manage multiple git repositories
+simultaneously. You can install it by executing the following commands:
 
-## ROCm Documentation
+```shell
+curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
+chmod a+x ~/bin/repo
+```
+Note: make sure ~/bin exists and it is part of your PATH
 
-ROCm Documentation is available online at
-[rocm.docs.amd.com](https://rocm.docs.amd.com). Source code for the documenation
-is located in the docs folder of most repositories that are part of ROCm.
-
-### How to build documentation via Sphinx
-
-```bash
-cd docs
-
-pip3 install -r sphinx/requirements.txt
-
-python3 -m sphinx -T -E -b html -d _build/doctrees -D language=en . _build/html
+#### Cloning the code
+```shell
+mkdir ROCm && cd ROCm
+repo init -u https://github.com/RadeonOpenCompute/ROCm.git -b roc-1.3.0
+repo sync
 ```
 
-## Older ROCm™ Releases
+#### Closed Source Components
+The ROCm platform relies on a few closed source components to provide legacy
+functionality like HSAIL finalization and debugging/profiling support. These
+components are only available through the ROCm repositories, and will either be
+deprecated or become open source components in the future. These components are
+made available in the following packages:
 
-For release information for older ROCm™ releases, refer to
-[CHANGELOG](./CHANGELOG.md).
+*  hsa-ext-rocr-dev

RELEASE.md

@@ -1,33 +0,0 @@
-# Release Notes
-<!-- Do not edit this file! This file is autogenerated with -->
-<!--   tools/autotag/tag_script.py                          -->
-
-<!-- Disable lints since this is an auto-generated file.    -->
-<!-- markdownlint-disable blanks-around-headers             -->
-<!-- markdownlint-disable no-duplicate-header               -->
-<!-- markdownlint-disable no-blanks-blockquote              -->
-<!-- markdownlint-disable ul-indent                         -->
-<!-- markdownlint-disable no-trailing-spaces                -->
-
-<!-- spellcheck-disable -->
-
-The release notes for the ROCm platform.
-
--------------------
-
-## ROCm 5.6.1
-<!-- markdownlint-disable first-line-h1 -->
-<!-- markdownlint-disable no-duplicate-header -->
-
-### What's New in This Release
-
-ROCm 5.6.1 is a point release with several bug fixes in the HIP runtime.
-
-## HIP 5.6.1 (for ROCm 5.6.1)
-
-### Fixed Defects
-
-- *hipMemcpy* device-to-device (intra device) is now asynchronous with respect to the host
-- Enabled xnack+ check in HIP catch2 tests hang when executing tests
-- Memory leak when code object files are loaded/unloaded via hipModuleLoad/hipModuleUnload APIs
-- Using *hipGraphAddMemFreeNode* no longer results in a crash

default.xml

@@ -1,75 +1,27 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <manifest>
+
     <remote name="roc-github"
-fetch="https://github.com/RadeonOpenCompute/" />
-    <remote name="rocm-devtools"
-fetch="https://github.com/ROCm-Developer-Tools/" />
-    <remote name="rocm-swplat"
-fetch="https://github.com/ROCmSoftwarePlatform/" />
-    <remote name="gpuopen-libs"
-fetch="https://github.com/GPUOpen-ProfessionalCompute-Libraries/" />
-    <remote name="gpuopen-tools"
-fetch="https://github.com/GPUOpen-Tools/" />
-    <remote name="KhronosGroup"
-fetch="https://github.com/KhronosGroup/" />
-    <default revision="refs/tags/rocm-5.6.1"
-     remote="roc-github"
-     sync-c="true"
-     sync-j="4" />
-<!--list of projects for ROCM-->
-    <project name="ROCK-Kernel-Driver" remote="roc-github" />
-    <project name="ROCT-Thunk-Interface" remote="roc-github" />
-    <project name="ROCR-Runtime" remote="roc-github" />
-    <project name="rocm_smi_lib" remote="roc-github" />
-    <project name="rocm-core" remote="roc-github" />
-    <project name="rocm-cmake" remote="roc-github" />
-    <project name="rocminfo" remote="roc-github" />
-    <project name="rocprofiler" remote="rocm-devtools" />
-    <project name="roctracer" remote="rocm-devtools" />
-    <project path="ROCm-OpenCL-Runtime/api/opencl/khronos/icd" name="OpenCL-ICD-Loader" remote="KhronosGroup" revision="6c03f8b58fafd9dd693eaac826749a5cfad515f8" />
-    <project name="clang-ocl" remote="roc-github" />
-<!--HIP Projects-->
-    <project name="HIP" remote="rocm-devtools" />
-    <project name="clr" remote="rocm-devtools" />
-    <project name="HIP-Examples" remote="rocm-devtools" />
-    <project name="HIPIFY" remote="rocm-devtools" />
-    <project name="HIPCC" remote="rocm-devtools" />
-<!-- The following projects are all associated with the AMDGPU LLVM compiler -->
-    <project name="llvm-project" remote="roc-github" />
-    <project name="ROCm-Device-Libs" remote="roc-github" />
-    <project name="ROCm-CompilerSupport" remote="roc-github" />
-    <project name="rocr_debug_agent" remote="rocm-devtools" />
-    <project name="rocm_bandwidth_test" remote="roc-github" />
-    <project name="half" remote="rocm-swplat" revision="37742ce15b76b44e4b271c1e66d13d2fa7bd003e" />
-    <project name="RCP" remote="gpuopen-tools" revision="3a49405a1500067c49d181844ec90aea606055bb" />
-<!-- gdb projects -->
-    <project name="ROCgdb" remote="rocm-devtools" />
-    <project name="ROCdbgapi" remote="rocm-devtools" />
-<!-- ROCm Libraries -->
-    <project name="rdc" remote="roc-github" />
-    <project groups="mathlibs" name="rocBLAS" remote="rocm-swplat" />
-    <project groups="mathlibs" name="Tensile" remote="rocm-swplat" />
-    <project groups="mathlibs" name="hipBLAS" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocFFT" remote="rocm-swplat" />
-    <project groups="mathlibs" name="hipFFT" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocRAND" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocSPARSE" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocSOLVER" remote="rocm-swplat" />
-    <project groups="mathlibs" name="hipSOLVER" remote="rocm-swplat" />
-    <project groups="mathlibs" name="hipSPARSE" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocALUTION" remote="rocm-swplat" />
-    <project name="MIOpen" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rccl" remote="rocm-swplat" />
-    <project name="MIVisionX" remote="gpuopen-libs" />
-    <project groups="mathlibs" name="rocThrust" remote="rocm-swplat" />
-    <project groups="mathlibs" name="hipCUB" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocPRIM" remote="rocm-swplat" />
-    <project groups="mathlibs" name="rocWMMA" remote="rocm-swplat" />
-    <project name="hipfort" remote="rocm-swplat" />
-    <project name="AMDMIGraphX" remote="rocm-swplat" />
-    <project name="ROCmValidationSuite" remote="rocm-devtools" />
-<!-- Projects for OpenMP-Extras -->
-    <project name="aomp" path="openmp-extras/aomp" remote="rocm-devtools" />
-    <project name="aomp-extras" path="openmp-extras/aomp-extras" remote="rocm-devtools" />
-    <project name="flang" path="openmp-extras/flang" remote="rocm-devtools" />
+            fetch="http://git@github.com/RadeonOpenCompute/" />
+    <remote name="pctools-github"
+            fetch="http://git@github.com/GPUOpen-ProfessionalCompute-Tools/" />
+
+    <default revision="refs/tags/roc-1.3.0"
+             remote="roc-github"
+             sync-j="4" />
+
+    <project path="llvm" name="llvm" />
+    <project path="llvm-amdgpu-assembler-extra" name="LLVM-AMDGPU-Assembler-Extra" />
+    <project path="clang" name="clang" />
+
+    <project path="hcc" name="hcc" />
+    <project path="ROCT-Thunk-Interface" name="ROCT-Thunk-Interface" />
+    <project path="ROCK-Kernel-Driver" name="ROCK-Kernel-Driver" />
+    <project path="ROC-smi" name="ROC-smi" />
+    <project path="ROCnRDMA" name="ROCnRDMA" />
+    <project path="rdma-perftest" name="rdma-perftest" />
+    <project path="ROCR-Runtime" name="ROCR-Runtime" />
+    <project path="HIP" remote="pctools-github" name="HIP" />
+    <project path="HIP-Examples" remote="pctools-github" name="HIP-Examples" />
+
 </manifest>

docs/404.md

@@ -1,6 +0,0 @@
-# 404 Page Not Found
-
-Page could not be found.
-
-Return to [home](./index) or please use the links from the sidebar to find what
-you are looking for.

docs/about.md

@@ -1,74 +0,0 @@
-# About ROCm Documentation
-
-ROCm documentation is made available under open source [licenses](licensing.md).
-Documentation is built using open source toolchains. Contributions to our
-documentation is encouraged and welcome. As a contributor, please familiarize
-yourself with our documentation toolchain.
-
-## Read The Docs
-
-[Read the Docs](https://docs.readthedocs.io/en/stable/) is our front end for the
-our documentation. By front end, this is the tool that serves our HTML based
-documentation to our end users.
-
-## Doxygen
-
-[Doxygen](https://www.doxygen.nl/) is the most common inline code documentation
-standard. ROCm projects are use Doxygen for public API documentation (unless the
-upstream project is using a different tool).
-
-## Sphinx
-
-[Sphinx](https://www.sphinx-doc.org/en/master/) is a documentation generator
-originally used for python. It is now widely used in the Open Source community.
-Originally, sphinx supported RST based documentation. Markdown support is now
-available. ROCm documentation plans to default to markdown for new projects.
-Existing projects using RST are under no obligation to convert to markdown. New
-projects that believe markdown is not suitable should contact the documentation
-team prior to selecting RST.
-
-### MyST
-
-[Markedly Structured Text (MyST)](https://myst-tools.org/docs/spec) is an extended
-flavor of Markdown ([CommonMark](https://commonmark.org/)) influenced by reStructuredText (RST) and Sphinx.
-It is integrated via [`myst-parser`](https://myst-parser.readthedocs.io/en/latest/).
-A cheat sheet that showcases how to use the MyST syntax is available over at [the Jupyter
-reference](https://jupyterbook.org/en/stable/reference/cheatsheet.html).
-
-### Sphinx Theme
-
-ROCm is using the
-[Sphinx Book Theme](https://sphinx-book-theme.readthedocs.io/en/latest/). This
-theme is used by Jupyter books. ROCm documentation applies some customization
-include a header and footer on top of the Sphinx Book Theme. A future custom
-ROCm theme will be part of our documentation goals.
-
-### Sphinx Design
-
-Sphinx Design is an extension for sphinx based websites that add design
-functionality. Please see the documentation
-[here](https://sphinx-design.readthedocs.io/en/latest/index.html). ROCm
-documentation uses sphinx design for grids, cards, and synchronized tabs.
-Other features may be used in the future.
-
-### Sphinx External TOC
-
-ROCm uses the
-[sphinx-external-toc](https://sphinx-external-toc.readthedocs.io/en/latest/intro.html)
-for our navigation. This tool allows a YAML file based left navigation menu. This
-tool was selected due to its flexibility that allows scripts to operate on the
-YAML file. Please transition to this file for the project's navigation. You can
-see the `_toc.yml.in` file in this repository in the docs/sphinx folder for an
-example.
-
-### Breathe
-
-Sphinx uses [Breathe](https://www.breathe-doc.org/) to integrate Doxygen
-content.
-
-## `rocm-docs-core` pip package
-
-[rocm-docs-core](https://github.com/RadeonOpenCompute/rocm-docs-core) is an AMD
-maintained project that applies customization for our documentation. This
-project is the tool most ROCm repositories will use as part of the documentation
-build.

docs/conf.py

@@ -1,98 +0,0 @@
-# Configuration file for the Sphinx documentation builder.
-#
-# This file only contains a selection of the most common options. For a full
-# list see the documentation:
-# https://www.sphinx-doc.org/en/master/usage/configuration.html
-
-import shutil
-
-from rocm_docs import ROCmDocs
-
-
-shutil.copy2('../CONTRIBUTING.md','./contributing.md')
-shutil.copy2('../RELEASE.md','./release.md')
-# Keep capitalization due to similar linking on GitHub's markdown preview.
-shutil.copy2('../CHANGELOG.md','./CHANGELOG.md')
-
-latex_engine = "xelatex"
-
-# configurations for PDF output by Read the Docs
-project = "ROCm Documentation"
-author = "Advanced Micro Devices, Inc."
-copyright = "Copyright (c) 2023 Advanced Micro Devices, Inc. All rights reserved."
-version = "5.6.1"
-release = "5.6.1"
-
-
-setting_all_article_info = True
-all_article_info_os = ["linux", "windows"]
-all_article_info_author = ""
-
-# pages with specific settings
-article_pages = [
-    {
-        "file":"release",
-        "os":["linux", "windows"],
-        "date":"2023-07-27"
-    },
-
-    {"file":"deploy/linux/index", "os":["linux"]},
-    {"file":"deploy/linux/install_overview", "os":["linux"]},
-    {"file":"deploy/linux/prerequisites", "os":["linux"]},
-    {"file":"deploy/linux/quick_start", "os":["linux"]},
-    {"file":"deploy/linux/install", "os":["linux"]},
-    {"file":"deploy/linux/upgrade", "os":["linux"]},
-    {"file":"deploy/linux/uninstall", "os":["linux"]},
-    {"file":"deploy/linux/package_manager_integration", "os":["linux"]},
-    {"file":"deploy/docker", "os":["linux"]},
-    
-    {"file":"deploy/windows/cli/index", "os":["windows"]},
-    {"file":"deploy/windows/cli/install", "os":["windows"]},
-    {"file":"deploy/windows/cli/uninstall", "os":["windows"]},
-    {"file":"deploy/windows/cli/upgrade", "os":["windows"]},
-    {"file":"deploy/windows/gui/index", "os":["windows"]},
-    {"file":"deploy/windows/gui/install", "os":["windows"]},
-    {"file":"deploy/windows/gui/uninstall", "os":["windows"]},
-    {"file":"deploy/windows/gui/upgrade", "os":["windows"]},
-    {"file":"deploy/windows/index", "os":["windows"]},
-    {"file":"deploy/windows/prerequisites", "os":["windows"]},
-    {"file":"deploy/windows/quick_start", "os":["windows"]},
-
-    {"file":"release/gpu_os_support", "os":["linux"]},
-    {"file":"release/windows_support", "os":["windows"]},
-    {"file":"release/docker_support_matrix", "os":["linux"]},
-    
-    {"file":"reference/gpu_libraries/communication", "os":["linux"]},
-    {"file":"reference/ai_tools", "os":["linux"]},
-    {"file":"reference/management_tools", "os":["linux"]},
-    {"file":"reference/validation_tools", "os":["linux"]},
-    {"file":"reference/framework_compatibility/framework_compatibility", "os":["linux"]},
-    {"file":"reference/computer_vision", "os":["linux"]},
-    
-    {"file":"how_to/deep_learning_rocm", "os":["linux"]},
-    {"file":"how_to/gpu_aware_mpi", "os":["linux"]},
-    {"file":"how_to/magma_install/magma_install", "os":["linux"]},
-    {"file":"how_to/pytorch_install/pytorch_install", "os":["linux"]},
-    {"file":"how_to/system_debugging", "os":["linux"]},
-    {"file":"how_to/tensorflow_install/tensorflow_install", "os":["linux"]},
-
-    {"file":"examples/machine_learning", "os":["linux"]},
-    {"file":"examples/inception_casestudy/inception_casestudy", "os":["linux"]},
-    
-    {"file":"understand/file_reorg", "os":["linux"]},
-
-    {"file":"understand/isv_deployment_win", "os":["windows"]},
-]
-
-external_toc_path = "./sphinx/_toc.yml"
-
-docs_core = ROCmDocs("ROCm 5.6.1 Documentation Home")
-docs_core.setup()
-
-external_projects_current_project = "rocm"
-
-for sphinx_var in ROCmDocs.SPHINX_VARS:
-    globals()[sphinx_var] = getattr(docs_core, sphinx_var)
-html_theme_options = {
-    "link_main_doc": False
-}

docs/deploy/docker.md

@@ -1,90 +0,0 @@
-# Deploy ROCm Docker containers
-
-## Prerequisites
-
-Docker containers share the kernel with the host operating system, therefore the
-ROCm kernel-mode driver must be installed on the host. Please refer to
-{ref}`using-the-package-manager` on installing `amdgpu-dkms`. The other
-user-space parts (like the HIP-runtime or math libraries) of the ROCm stack will
-be loaded from the container image and don't need to be installed to the host.
-
-(docker-access-gpus-in-container)=
-
-## Accessing GPUs in containers
-
-In order to access GPUs in a container (to run applications using HIP, OpenCL or
-OpenMP offloading) explicit access to the GPUs must be granted.
-
-The ROCm runtimes make use of multiple device files:
-
-- `/dev/kfd`: the main compute interface shared by all GPUs
-- `/dev/dri/renderD<node>`: direct rendering interface (DRI) devices for each
-  GPU. **`<node>`** is a number for each card in the system starting from 128.
-
-Exposing these devices to a container is done by using the
-[`--device`](https://docs.docker.com/engine/reference/commandline/run/#device)
-option, i.e. to allow access to all GPUs expose `/dev/kfd` and all
-`/dev/dri/renderD` devices:
-
-```shell
-docker run --device /dev/kfd --device /dev/renderD128 --device /dev/renderD129 ...
-```
-
-More conveniently, instead of listing all devices, the entire `/dev/dri` folder
-can be exposed to the new container:
-
-```shell
-docker run --device /dev/kfd --device /dev/dri
-```
-
-Note that this gives more access than strictly required, as it also exposes the
-other device files found in that folder to the container.
-
-(docker-restrict-gpus)=
-
-### Restricting a container to a subset of the GPUs
-
-If a `/dev/dri/renderD` device is not exposed to a container then it cannot use
-the GPU associated with it; this allows to restrict a container to any subset of
-devices.
-
-For example to allow the container to access the first and third GPU start it
-like:
-
-```shell
-docker run --device /dev/kfd --device /dev/dri/renderD128 --device /dev/dri/renderD130 <image>
-```
-
-### Additional Options
-
-The performance of an application can vary depending on the assignment of GPUs
-and CPUs to the task. Typically, `numactl` is installed as part of many HPC
-applications to provide GPU/CPU mappings. This Docker runtime option supports
-memory mapping and can improve performance.
-
-```shell
---security-opt seccomp=unconfined
-```
-
-This option is recommended for Docker Containers running HPC applications.
-
-```shell
-docker run --device /dev/kfd --device /dev/dri --security-opt seccomp=unconfined ...
-```
-
-## Docker images in the ROCm ecosystem
-
-### Base images
-
-<https://github.com/RadeonOpenCompute/ROCm-docker> hosts images useful for users
-wishing to build their own containers leveraging ROCm. The built images are
-available from [Docker Hub](https://hub.docker.com/u/rocm). In particular
-`rocm/rocm-terminal` is a small image with the prerequisites to build HIP
-applications, but does not include any libraries.
-
-### Applications
-
-AMD provides pre-built images for various GPU-ready applications through its
-Infinity Hub at <https://www.amd.com/en/technologies/infinity-hub>.
-Examples for invoking each application and suggested parameters used for
-benchmarking are also provided there.

docs/deploy/linux/index.md

@@ -1,53 +0,0 @@
-# Deploy ROCm on Linux
-
-Start with {doc}`/deploy/linux/quick_start` or follow the detailed
-instructions below.
-
-## Prepare to Install
-
-::::{grid} 1 1 2 2
-:gutter: 1
-
-:::{grid-item-card} Prerequisites
-:link: prerequisites
-:link-type: doc
-
-The prerequisites page lists the required steps *before* installation.
-:::
-
-:::{grid-item-card} Install Choices
-:link: install_overview
-:link-type: doc
-
-Package manager vs AMDGPU Installer
-
-Standard Packages vs Multi-Version Packages
-:::
-
-::::
-
-## Choose your install method
-
-::::{grid} 1 1 2 2
-:gutter: 1
-
-:::{grid-item-card} Package Manager
-:link: os-native/index
-:link-type: doc
-
-Directly use your distribution's package manager to install ROCm.
-:::
-
-:::{grid-item-card} AMDGPU Installer
-:link: installer/index
-:link-type: doc
-
-Use an installer tool that orchestrates changes via the package
-manager.
-:::
-
-::::
-
-## See Also
-
-- {doc}`/release/gpu_os_support`

docs/deploy/linux/install_overview.md

@@ -1,71 +0,0 @@
-# ROCm Installation Options (Linux)
-
-Users installing ROCm must choose between various installation options. A new
-user should follow the [Quick Start guide](./quick_start).
-
-## Package Manager versus AMDGPU Installer?
-
-ROCm supports two methods for installation:
-
-- Directly using the Linux distribution's package manager
-- The `amdgpu-install` script
-
-There is no difference in the final installation state when choosing either
-option.
-
-Using the distribution's package manager lets the user install,
-upgrade and uninstall using familiar commands and workflows. Third party
-ecosystem support is the same as your OS package manager.
-
-The `amdgpu-install` script is a wrapper around the package manager. The same
-packages are installed by this script as the package manager system.
-
-The installer automates the installation process for the AMDGPU
-and ROCm stack. It handles the complete installation process
-for ROCm, including setting up the repository, cleaning the system, updating,
-and installing the desired drivers and meta-packages. Users who are
-less familiar with the package manager can choose this method for ROCm
-installation.
-
-(installation-types)=
-
-## Single Version ROCm install versus Multi-Version
-
-ROCm packages are versioned with both semantic versioning that is package
-specific and a ROCm release version.
-
-### Single-version Installation
-
-The single-version ROCm installation refers to the following:
-
-- Installation of a single instance of the ROCm release on a system
-- Use of non-versioned ROCm meta-packages
-
-### Multi-version Installation
-
-The multi-version installation refers to the following:
-
-- Installation of multiple instances of the ROCm stack on a system. Extending
-  the package name and its dependencies with the release version adds the
-  ability to support multiple versions of packages simultaneously.
-- Use of versioned ROCm meta-packages.
-
-```{attention}
-ROCm packages that were previously installed from a single-version installation
-must be removed before proceeding with the multi-version installation to avoid
-conflicts.
-```
-
-```{note}
-Multiversion install is not available for the kernel driver module, also referred to as AMDGPU.
-```
-
-The following image demonstrates the difference between single-version and
-multi-version ROCm installation types:
-
-```{figure-md} install-types
-
-<img src="/data/deploy/linux/image.001.png" alt="">
-
-ROCm Installation Types
-```

docs/deploy/linux/installer/index.md

@@ -1,31 +0,0 @@
-# AMDGPU Install Script
-
-::::{grid} 2 3 3 3
-:gutter: 1
-
-:::{grid-item-card} Install
-:link: install
-:link-type: doc
-
-How to install ROCm?
-:::
-
-:::{grid-item-card} Upgrade
-:link: upgrade
-:link-type: doc
-
-Instructions for upgrading an existing ROCm installation.
-:::
-
-:::{grid-item-card} Uninstall
-:link: uninstall
-:link-type: doc
-
-Steps for removing ROCm packages, libraries and tools.
-:::
-
-::::
-
-## See Also
-
-- {doc}`/release/gpu_os_support`