aarch64, fix gdb with linux-custom

README.md

@@ -291,7 +291,7 @@ And then tell GDB where the module was loaded with:
 
 The portability of the kernel and toolchains is amazing: change an option and most things magically work on completely different hardware.
 
-### ARM
+### arm
 
 First build:
 
@@ -312,7 +312,21 @@ TODOs:
 -   only managed to run in the terminal interface (but weirdly a blank QEMU window is still opened)
 -   GDB not connecting to KGDB. Possibly linked to `-serial stdio`. See also: <https://stackoverflow.com/questions/14155577/how-to-use-kgdb-on-arm>
 
-### MIPS
+### aarch64
+
+    ./run -a aarch64
+
+TODOs:
+
+-   GDB gives a ton of messages:
+
+        no module object found for ''
+
+    when you connect. `Ctrl + C` then `c` works though.
+
+-   How to add devices to `-M virt` as we did for `-M versatilepb`
+
+### mips64
 
     ./run -a mips64