Converted adoc to md

content/documentation/Clusterboard/Layout.md

@@ -0,0 +1,54 @@
+---
+title: "Layout"
+draft: false
+menu:
+  docs:
+    title:
+    parent: "Clusterboard"
+    identifier: "Clusterboard/Layout"
+    weight: 1
+---
+
+{{< figure src="/documentation/Clusterboard/images/clusterboard_labels.png" title="The Clusterboard with labels" width="400" >}}
+
+| Label | Description |
+| --- | --- |
+| 1 | Barrel-type DC jack (6.3&nbsp;mm outer diameter, 3.0&nbsp;mm inner diameter) for a +5&nbsp;V, 15&nbsp;A power supply |
+| 2 | Gigabit Ethernet port |
+| 3 | Reset button, for all seven modules |
+| 4 | Holder for two non-rechargeable 1.5&nbsp;V AA-size batteries, providing backup for the real-time clock (RTC) on all modules |
+| 5 | Connector for an eMMC module, for the first SOPINE or SOEDGE module |
+| 6 | Slot for a SOPINE or SOEDGE module |
+| 7 | USB&nbsp;2.0 Type-A socket |
+| 8 | MicroUSB Type-B USB&nbsp;2.0 socket |
+| 9 | Activity LED |
+| 10 | 20-pin expansion connector |
+| 11 | Three-pin connector for a lithium battery |
+| 12 | RTL8211E Gigabit Ethernet PHY, with two status LEDs |
+| 13 | Gigabit Ethernet Switch (RTL8370N) |
+| 14 | 24-pin ATX Power Connector |
+| 15 | Two-pin connector for a switch/button that turns on connected ATX power supply |
+| 16 | 5&nbsp;V power output for hard disk drives (optional) |
+| 17 | Places for soldering two resistors (optional, for use with an ATX power suppply that requires dummy load on 3.3&nbsp;V and 12&nbsp;V rails) |
+
+For the part 4, please see the important note in the [specifications](/documentation/Clusterboard/Further_information/Specifications) page. For the part 11, please see the notes in the [hardware revisions](/documentation/Clusterboard/Further_information/Revisions) page. Parts 6 to 12 exist separately for each of all seven SOPINE or SOEDGE modules.
+
+## 20-pin Expansion Connector
+
+The 20-pin expansion connector is the part 10 decribed in the section above, available for each SOPINE or SOEDGE module. There is an unofficial description of the pinout in [this forum thread](https://forum.pine64.org/showthread.php?tid=5713). The unofficial pinout is also visible directly in [this picture](https://forum.pine64.org/attachment.php?aid=1111).
+
+## SOPINE Module
+
+{{< figure src="/documentation/SOPINE/images/sopine_front_labels.png" title="Front view of the SOPINE module with labels" width="400" >}}
+
+{{< figure src="/documentation/SOPINE/images/sopine_back_labels.png" title="Rear view of the SOPINE module with labels" width="400" >}}
+
+| Label | Description |
+| --- | --- |
+| 1 | A64 SoC |
+| 2 | 2 GB of DDR3 RAM |
+| 3 | AXP803 PMIC |
+| 4 | Edge connector, the same as on SO-DIMM modules |
+| 5 | Power LED |
+| 6 | microSD card slot |
+| 7 | SPI flash memory |

content/documentation/General/Mainline_Hardware_Decoding.adoc

@@ -9,7 +9,9 @@ menu:
     weight: 
 ---
 
-TIP: This page is incomplete, you're welcome to improve it.
+{{% admonition type="note" %}}
+This page is incomplete, you're welcome to improve it.
+{{% /admonition %}}
 
 *Mainline Hardware Decoding* refers to video decoding done using hardware accelerators on the mainline Linux kernel (i.e. what sits in Linus' tree).
 

content/documentation/General/Overclocking.adoc

@@ -13,9 +13,13 @@ menu:
  There is the possibility of damaging your equipment by overclocking. Do so at your own risk!
 {{< /admonition >}}
 
-TIP: This page is incomplete, you're welcome to improve it.
+{{% admonition type="note" %}}
+This page is incomplete, you're welcome to improve it.
+{{% /admonition %}}
 
-TIP: All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it https://elinux.org/Device_Tree_Reference[here].
+{{% admonition type="note" %}}
+All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it https://elinux.org/Device_Tree_Reference[here].
+{{% /admonition %}}
 
 Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default, usually while putting out more heat and using more power (You can also downclock to possibly reduce power consumption and thermals at the cost of performance). It is highly recommended that you avoid overvolting the device, as that has a high risk of damaging the hardware, hence the warning at the beginning of this page. However, just some slight overclocks without the added voltage can not only improve performance, but not carry as much risk (Still: Do at your own risk!). It should be noted however that overclocking can cause instability, so you will need to test and see what values work best with your device (There is a silicon lottery for the Pinephone's hardware).
 
@@ -59,9 +63,13 @@ Save the DTS file, and recompile the DTB. In order to check if the overclock was
  The file may be slightly different and you may need to enter the values as hexadecimals
 {{< /admonition >}}
 
-TIP: The GPU appears to run stable overclocked to 540 Mhz, however more testing with a wider group of devices is needed.
+{{% admonition type="note" %}}
+The GPU appears to run stable overclocked to 540 Mhz, however more testing with a wider group of devices is needed.
+{{% /admonition %}}
 
-TIP: Remember to run a benchmark tool (such as glmark2-es2) to help check stability.
+{{% admonition type="note" %}}
+Remember to run a benchmark tool (such as glmark2-es2) to help check stability.
+{{% /admonition %}}
 
 === CPU
 
@@ -107,17 +115,23 @@ The table above shows the valid voltages provided by the AXP803 PMIC on DCDC2 (u
  The user _somefoo_ was able to undervolt the PinePhone at each frequency operation point by at least -100mv. The A64 set to 1.152Ghz runs at 1.18v instead of the standard 1.3v, dropping the power usage by ~0.7w under full single threaded load|The silicon lottery will dictate how well you can undervolt.
 {{< /admonition >}}
 
-TIP: The exact voltages and frequencies that you can achieve will depend on your device. Make sure to run stress tests (such as _stress-ng_) to ensure stability.
+{{% admonition type="note" %}}
+The exact voltages and frequencies that you can achieve will depend on your device. Make sure to run stress tests (such as _stress-ng_) to ensure stability.
+{{% /admonition %}}
 
 === DRAM
 
 {{< admonition type="warning" >}}
  It is not recommended to exceed 667 MHz clockspeed on the DRAM. 648MHz is likely the upper limit.
 {{< /admonition >}}
 
-TIP: Make sure to set your DRAM to a multiple of 24.
+{{% admonition type="note" %}}
+Make sure to set your DRAM to a multiple of 24.
+{{% /admonition %}}
 
-TIP: The current frequency your DRAM is running at can be found using this command: `cat /proc/device-tree/memory/ram_freq`
+{{% admonition type="note" %}}
+The current frequency your DRAM is running at can be found using this command: `cat /proc/device-tree/memory/ram_freq`
+{{% /admonition %}}
 
 When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory. The A64's maximum ram clockspeed falls just short of 667MHz. This may be unstable on your device however.