From b05c4154d173e163efd3023ac8c3f6d04b5df207 Mon Sep 17 00:00:00 2001 From: rcarteraz Date: Sun, 17 Mar 2024 09:48:18 -0700 Subject: [PATCH] add footnote regarding pi zero --- .../linux-native-hardware/linux-native-hardware.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/hardware/devices/linux-native-hardware/linux-native-hardware.mdx b/docs/hardware/devices/linux-native-hardware/linux-native-hardware.mdx index 3833bd8e..3b7536ce 100644 --- a/docs/hardware/devices/linux-native-hardware/linux-native-hardware.mdx +++ b/docs/hardware/devices/linux-native-hardware/linux-native-hardware.mdx @@ -12,11 +12,12 @@ This guide outlines the setup of Meshtastic on Linux-native devices, utilizing p Before proceeding with the setup, ensure the device meets the following requirements: ### Tested Devices -- Raspberry Pi zero, zero 2 , 3,4, Pi 400, and Pi 5. -- Ubuntu 22.04 X86_64 with a CH341-SX1262 DIY dongle.[^1] +- Raspberry Pi zero, zero 2 , 3,4, Pi 400, and Pi 5.[^1] +- Ubuntu 22.04 X86_64 with a CH341-SX1262 DIY dongle.[^2] - Debian GNU/Linux trixie/sid riscv64 on Cvitek CV180X ASIC, C906 (Milk-V Duo), on the SPI bus. -[^1]: **Limited Functionality with CH341-SX1262 Device:** Please be aware that the CH341-SX1262 device is currently experiencing partial functionality issues. For reasons yet to be determined, this device struggles with sending packets larger than a few bytes. +[^1]: While the Raspberry Pi Zero has been tested with meshtasticd, building as a native ARM32 binary has proven challenging. As a workaround, consider building on a Raspberry Pi 4 or 5 with a 32-bit OS and copying the output file to the Pi Zero. +[^2]: **Limited Functionality with CH341-SX1262 Device:** Please be aware that the CH341-SX1262 device is currently experiencing partial functionality issues. For reasons yet to be determined, this device struggles with sending packets larger than a few bytes. ### Hardware Compatibility - Tested radios include Waveshare SX126X, Adafruit RFM9x, and Elecrow Lora RFM95 IOT.