machines: Move special TC machines to meta-petalinux

The special toolchains are really only applicable to a PetaLinux/Vitis
toolchain build.

Signed-off-by: Mark Hatle <mark.hatle@amd.com>

1 files changed, 1 insertions, 14 deletions

diff --git a/meta-xilinx-standalone/README.md b/meta-xilinx-standalone/README.md
index 6193f015..8834a87b 100644
--- a/meta-xilinx-standalone/README.md
+++ b/meta-xilinx-standalone/README.md
@@ -1,7 +1,7 @@
 # meta-xilinx-standalone
 
 This layer is meant to augment Yocto/OE functionality to provide a 
-Baremetal/Standalone Toolchain as well as a generic version of various
+Baremetal/Standalone distribution as well as a generic version of various
 firmware that is required to boot a ZynqMP or Versal system.
 
 For optimized versions of the firmware and additional components you must
@@ -14,19 +14,6 @@ configuration build, or a multiconfig build.  A multiconfig build, along
 with the MACHINES defined in meta-xilinx-bsps will automate the generation
 of certain firmwares.
 
-## Toolchains
-
-To build standalone toolchains similar to those embedded with the
-Xilinx xsct tooling:
-
-Use one of the custom machines:
-  aarch32-tc - 32-bit ARM toolchains (various)
-  aarch64-tc - 64-bit ARM toolchains (various)
-  arm-rm-tc  - ARM Cortex-R (and various)
-  microblaze-tc - Microblaze toolchains (various)
-
-MACHINE=<machine> DISTRO=xilinx-standalone bitbake meta-toolchain
-
 ## Standalone Firmware
 
 The standalone firmware is a genericly configured firmware, it can be