diff options
Diffstat (limited to '')
-rw-r--r-- | 12.-Appendix.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/12.-Appendix.md b/12.-Appendix.md index 9ace66e..a2657f7 100644 --- a/12.-Appendix.md +++ b/12.-Appendix.md @@ -96,7 +96,7 @@ It is up to you the programmer to ensure that the inputs are valid. Entering inc * Intel i5, i7 on Ubuntu * Dell Wyse Thin Clients * Orange Pi 4 - Note: The OPI4 is sensitive to USB cables. Needs a short high quality USB data cable. Will not work with long and/or poor quality USB data cables. -* Orange Pi 5 - Note that there is no WiFi on this device. We recommend using a M2 or PCIE add on card, rather than USB WiFi dongle. KrakenSDR may not work properly if the USB bandwidth is shared by another high bandwidth device. +* Orange Pi 5 / 5B- Note that there is no WiFi on the standard device, but there is a '5B' version that includes WiFi which is recommended. For the Orange Pi 5 without WiFi we recommend using an M2 or PCIE add on card, rather than USB WiFi dongle. KrakenSDR may not work properly if the USB bandwidth is shared by another high bandwidth device like a WiFi stick. ### Virtualization @@ -104,7 +104,7 @@ It is up to you the programmer to ensure that the inputs are valid. Entering inc * Docker with ClearLinux ## Working but with major quirks -* Odroid N2/+ - Note: You must use the **BOTTOM USB port that is closest to the DC power barrel jack**. All other USB ports do not work for high data rate devices on this machine. Also requires a high quality USB cable. On this device every ~12 hours there is some USB glitch resulting in sample mis-alignment. This results in the DOA results going bad. If you have periodic recalibration turned ON (the default), it's not a huge deal, but you could be about 5 minutes with bad results. +* Odroid N2/+ - Note: You must use the **BOTTOM USB port that is closest to the DC power barrel jack**. All other USB ports do not work for high data rate devices on this machine. Also requires a high quality USB cable. On this device every ~12 hours there is some USB glitch resulting in sample mis-alignment. This results in the DOA results going bad. If you have periodic recalibration turned ON (the default), it's not a huge deal, but you could be running for about 5 minutes with bad results. ## Not Working * Tinkerboard - Unfortunately pure 32-bit ARM CPUs are not supported by Miniforge Conda. |