ARM_platforms.md

-This is about [[!tails_ticket 10972]].
+This is about tails/tails#10972.
+
+
+[[_TOC_]]
 
-[[!toc levels=3]]
 
 Related pages
 =============
 
-[[!map pages="blueprint/ARM_platforms/*"]]
+- [Acer Chromebook R 13 CB5-312T](ARM_platforms/Acer_Chromebook_R_13_CB5-312T)
+
+
+
 
 Pros & cons
 ===========
@@ -25,7 +30,7 @@ Pros & cons
     can in turn compromise Tails.
 
 * Most mobile touch devices, e.g. tablets, are based on ARM
-  these days ([[!tails_ticket 6064]]).
+  these days (tails/tails#6064).
 
 * Some concerns about (Intel) x86 technologies, like the Intel ME,
   might be less of a problem for the time being on ARM. This is no
@@ -51,7 +56,7 @@ Pros & cons
   state of things, it is hard to estimate the resources we would need
   to make it happen.
 
-* Tor Browser [[!tor_bug 12631 desc="is not supported on ARM yet"]].
+* Tor Browser [is not supported on ARM yet](https://bugs.torproject.org/12631).
 
 ## Other remarks
 
@@ -79,12 +84,12 @@ Useful, up-to-date lists of devices can be found there:
 
 Current (mid-2014 to early 2016) ARM Chromebooks have one of:
 
-* Nvidia's [[!wikipedia Tegra]] K1 T124 (32-bit), that has
-  [[!wikipedia ARM Cortex-A15]], that is ARMv7-A architecture; it has
+* Nvidia's [Tegra](https://en.wikipedia.org/wiki/Tegra) K1 T124 (32-bit), that has
+  [ARM Cortex-A15](https://en.wikipedia.org/wiki/ARM%20Cortex%2DA15), that is ARMv7-A architecture; it has
   VFPv4
 
-* [[!wikipedia ARM Cortex-A17]] (e.g.
-  in [[!wikipedia Rockchip_RK3288]] (32-bit), that is ARMv7-A
+* [ARM Cortex-A17](https://en.wikipedia.org/wiki/ARM%20Cortex%2DA17) (e.g.
+  in [Rockchip RK3288](https://en.wikipedia.org/wiki/Rockchip%5FRK3288) (32-bit), that is ARMv7-A
   architecture; it has VFPv4
 
 For Jessie,
@@ -109,10 +114,10 @@ for armhf.
 **Update** one year later — April 2017, some ARMv8 (64-bit) ones have
 appeared:
 
-* [[!wikipedia MediaTek]] MT8173 ([[!wikipedia PowerVR]] GX6250 GPU),
+* [MediaTek](https://en.wikipedia.org/wiki/MediaTek) MT8173 ([PowerVR](https://en.wikipedia.org/wiki/PowerVR) GX6250 GPU),
   e.g. in the Acer Chromebook R13 and Lenovo N23 Yoga Chromebook
 * [Rockchip_RK3399](https://en.wikipedia.org/wiki/Rockchip#RK33xx_series)
-  ([[!wikipedia Mali (GPU)]] T860 MP4 GPU), e.g. in the Samsung
+  ([Mali (GPU)](https://en.wikipedia.org/wiki/Mali%20%28GPU%29) T860 MP4 GPU), e.g. in the Samsung
   Chromebook Plus
 
 On the 32-bit front, a few RK3288-based tablets and media boxes keep
@@ -126,17 +131,17 @@ appearing, but the latest 32-bit ARM Chromebook was released in
 Let's see how current (early 2016) Debian supports ARM Chromebooks.
 
 * Acer Chromebook 13 (CB5-311), Tegra K1
-  - [[!debwiki InstallingDebianOn/Acer/Chromebook_13_CB5-311-T8BT]]
+  - [InstallingDebianOn/Acer/Chromebook 13 CB5-311-T8BT](https://wiki.debian.org/InstallingDebianOn/Acer/Chromebook_13_CB5-311-T8BT)
     suggests it may require a custom kernel
 * Asus Chromebook C201, Rockchip RK3288
-  - [[!debwiki InstallingDebianOn/Asus/C201]]
+  - [InstallingDebianOn/Asus/C201](https://wiki.debian.org/InstallingDebianOn/Asus/C201)
     suggests it may require a custom kernel
 * Asus Chromebook Flip, Rockchip RK3288
 * HP Chromebook 14 (some models), Tegra K1
 
 XXX: update this section with newer information, e.g. after
 we've managed to boot a Debian kernel on an
-[[Acer Chromebook R 13|ARM_platforms/Acer_Chromebook_R_13_CB5-312T]].
+[Acer Chromebook R 13](ARM_platforms/Acer_Chromebook_R_13_CB5-312T).
 
 ### How others handle it
 
@@ -198,3 +203,4 @@ available on ARM.
 
 XXX: is Coreboot or U-Boot installed on ARM Chromebooks?
 <https://www.coreboot.org/Chromebooks> lists only X86 devices.
+