From 853ad3763cf5b5f8f98d51df123977c4193c99b1 Mon Sep 17 00:00:00 2001 From: Markus Unterwaditzer Date: Fri, 6 Mar 2026 19:45:01 +0100 Subject: [PATCH] apply suggestions from code review (github UI is broken) --- doc/porting.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/porting.md b/doc/porting.md index 340097c..9a0fda0 100644 --- a/doc/porting.md +++ b/doc/porting.md @@ -17,7 +17,9 @@ Please don't open issues about supporting a new device, use GitHub discussions i ## Prerequisites: root shell, and /dev/diag -Rayhunter is a Linux binary that reads traffic from `/dev/diag`, which requires root. If either of those isn't available, Rayhunter can't work. Everything else (displays, buttons) is secondary, and we can deal with it later. +Rayhunter is a Linux binary that reads traffic from the Qualcomm diagnostic interface, which requires root. If either of those isn't available, Rayhunter can't work. Everything else (displays, buttons) is secondary, and we can deal with it later. + +In the devices we currently support `/dev/diag` is the interface for Qualcomm diagnostics and devices with this will be easiest to support. Newer Qualcomm modems expose the diagnostic interface over a USB gadget which is something we are working on support for, but do not currently have. Thus devices with the former diagnostic interface will be easier to port Rayhunter to. You can check ahead of purchase whether `/dev/diag` is available by ensuring the device has a Qualcomm MDM* chip. Other Qualcomm LTE chips might work but we haven't encountered one yet. Typically you will be able to get this information from [fcc.report](https://fcc.report), where either the chip is written down in some PDF or at least plainly visible in one of the teardown photos. Sometimes this information can also be found through teardown videos on YouTube. If you find that chip, there's a good chance (but no guarantee) `/dev/diag` is available.