diff --git a/src/sw_sup/artiq_legacy.md b/src/sw_sup/artiq_legacy.md
index a014973..af8e9ac 100644
--- a/src/sw_sup/artiq_legacy.md
+++ b/src/sw_sup/artiq_legacy.md
@@ -42,6 +42,18 @@ git checkout c590df48e0553a670e18ebf9d02047bfcfddb40d
 cd ..
 ```
 
+### If you need ARTIQ-6 on Kasli 2.0.2
+
+Due to a different I2C IO expander chip, ARTIQ-6 firmware may boot on a Kasli 2.0.2, but will not allow Ethernet connection (and possibly DRTIO as well).
+
+For that, before starting the development shell, patch the ARTIQ-6 with the [commit from ARTIQ-7 that added support for it](https://github.com/m-labs/artiq/commit/ce57d6c34680360da95465295044b1c4a51a4864):
+
+```shell
+cd artiq
+git cherry-pick ce57d6c34680360da95465295044b1c4a51a4864
+cd ..
+```
+
 ## Setting up the environment and building firmware
 
 Within ``fish`` shell (others may not work correctly), set up the ARTIQ build environment:
diff --git a/src/sw_sup/networking.md b/src/sw_sup/networking.md
index 53473b8..e2e8d41 100644
--- a/src/sw_sup/networking.md
+++ b/src/sw_sup/networking.md
@@ -16,7 +16,7 @@ a-la `I can't connect, please help`.
 6. SFP or Ethernet are not pushed til the end.
 7. Some weird bugs in Vivado, leading to not working SFP on certain combinations of builds and Kaslis (very rare)
 8. Running configured for external reference Kasli without external reference clock signal
-9. Using legacy firmware with newer hardware. ARTIQ-6 doesn't support Kasli v2.0.2
+9. Using legacy firmware with newer hardware. ARTIQ-6 doesn't support Kasli v2.0.2 (at least without the patch mentioned in the [legacy](artiq_legacy.md) article)
 10. Some other device in your network already reserved the configured IP address.
 
 ## Ways to diagnose