summaryrefslogtreecommitdiffstats
path: root/doc/hardware.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/hardware.rst')
-rw-r--r--doc/hardware.rst65
1 files changed, 50 insertions, 15 deletions
diff --git a/doc/hardware.rst b/doc/hardware.rst
index 117fb17..5c9a0df 100644
--- a/doc/hardware.rst
+++ b/doc/hardware.rst
@@ -46,10 +46,10 @@ It supports the following hardware:
hardware_v7a_beaglebone_black
hardware_v7a_nitrogen6x
hardware_v7a_riot
- hardware_v7a_raspi2
- hardware_v7a_raspi3
+ hardware_v7a_raspi23
hardware_v7a_udoo_neo
hardware_v7a_sama5d2
+ hardware_v7a_sama5d4
If you want to get DistroKit running on your ARMv7-A board which is not
listed above, here is a short overview of the generic way:
@@ -92,6 +92,25 @@ listed above, here is a short overview of the generic way:
Refer to the :ref:`ptx_dev_manual` for a more thorough documentation.
+v7a_noneon Platform
+-------------------
+
++-------------------------+------------------------------------------------+
+| platformconfig: | ``configs/platform-v7a_noneon/platformconfig`` |
++-------------------------+------------------------------------------------+
+| Toolchain architecture: | ``arm-v7a-linux-gnueabihf`` |
++-------------------------+------------------------------------------------+
+
+The v7a_noneon platform targets machines based on the ARMv7-A architecture
+which don't have support for the NEON SIMD extension.
+It supports the following hardware:
+
+.. toctree::
+ :maxdepth: 1
+
+ hardware_v7a_noneon_sama5d3
+
+
v8a Platform
------------
@@ -105,38 +124,39 @@ The v8a platform targets the ARMv8-A architecture.
The stuff from the v7a section above applies here accordingly.
-Currently DistroKit only supports a single board; the Marvell espressobin:
+Currently, DistroKit supports the following hardware:
.. toctree::
:maxdepth: 1
hardware_v8a_espressobin
+ hardware_v8a_rock3a
-rpi Platform
-------------
+rpi1 Platform
+-------------
-+-------------------------+-----------------------------------------+
-| platformconfig: | ``configs/platform-rpi/platformconfig`` |
-+-------------------------+-----------------------------------------+
-| Toolchain architecture: | ``arm-1136jfs-linux-gnueabihf`` |
-+-------------------------+-----------------------------------------+
++-------------------------+------------------------------------------+
+| platformconfig: | ``configs/platform-rpi1/platformconfig`` |
++-------------------------+------------------------------------------+
+| Toolchain architecture: | ``arm-1136jfs-linux-gnueabihf`` |
++-------------------------+------------------------------------------+
.. note::
- The rpi platform is currently not actively maintained,
+ The rpi1 platform is currently not actively maintained,
as RPi 1 has been superseded by newer models
which are supported in the v7a platform.
However, if you are targeting a RPi 1,
we will be happy to merge your patches anyways.
-The rpi platform has support for the Raspberry Pi 1 and Raspberry Pi Zero W,
+The rpi1 platform has support for the Raspberry Pi 1 and Raspberry Pi Zero W,
which is based on the Broadcom BCM2835 SoC (ARMv6):
.. toctree::
:maxdepth: 1
- hardware_rpi_raspi1
+ hardware_rpi1_raspi1
mips Platform
@@ -151,7 +171,22 @@ mips Platform
.. toctree::
:maxdepth: 1
- hardware_x86_64_qemu
+ hardware_mips_qemu
+
+
+mips Platform
+-------------
+
++-------------------------+--------------------------------------------+
+| platformconfig: | ``configs/platform-mipsel/platformconfig`` |
++-------------------------+--------------------------------------------+
+| Toolchain architecture: | ``mipsel-softfloat-linux-gnu`` |
++-------------------------+--------------------------------------------+
+
+.. toctree::
+ :maxdepth: 1
+
+ hardware_mipsel_qemu
x86_64 Platform
@@ -166,4 +201,4 @@ x86_64 Platform
.. toctree::
:maxdepth: 1
- hardware_mips_qemu
+ hardware_x86_64_qemu