Update README.md

diff --git a/README.md b/README.md
index 76492318c3515d2cfeaca47c208b32c0856dec20..d670abf95a0f44829d3b0d68bb31d6728b3df37c 100644 (file)
--- a/README.md
+++ b/README.md
@@ -38,9 +38,15 @@ More About What Works
 
 What You Need
 ---
-* A Raspberry Pi 3 or better is needed. At present, Shairport Sync will not run successfully on an original Pi or a Pi Zero.
+* A Raspberry Pi. See table below for tested devices, feel free to open an issue or pull request if you have Shairport Sync working on a device not listed here!
 * [`NQPTP`](https://github.com/mikebrady/nqptp) is needed and must be run as `root`. It will use ports `319` and `320`, normally reserved for [PTP](https://standards.ieee.org/standard/1588-2008.html) clocks. If you are using PTP clock services for something else, you can't install [`NQPTP`](https://github.com/mikebrady/nqptp) and so you can't use Shairport Sync.(FYI, most computers do not have a PTP clock running -- instead, they may use a [Network Timing Protocol (NTP)](http://www.ntp.org) service to keep the system clock synchronised with world time. However, as noted above, macOS _does_ use a PTP clock to support AirPlay 2.)
 
+| Tested              | Native Hardware Status | Docker Status |
+|---------------------|------------------------|---------------|
+| Raspberry Pi 4      | Working                | Working       |
+| Raspberry Pi 3      | Working                | Working.      |
+| Raspberry Pi Zero W | Untested               | Working but since the Pi Zero is low powered, issues can arise fairly quickly when trying to run additional programs. Total CPU usage sits at around 75% when using Shairport Sync.|
+
 Guides
 ---
 * A brief guide to building Shairport Sync for AirPlay 1 is available at [BUILDFORAP1.md](https://github.com/aillwee/shairport-sync/blob/development/BUILDFORAP1.md).