From a97581876ebcf07b9f4107315a267df9aa7b0e77 Mon Sep 17 00:00:00 2001
From: Jm Casler <jm@casler.org>
Date: Sun, 21 Nov 2021 09:31:51 -0800
Subject: [PATCH] Update FAQ, Driver information and S&F

---
 website/docs/getting-started/faq.md           | 11 +++++++----
 .../docs/getting-started/flashing-esp32.md    |  2 ++
 .../docs/software/plugins/store-forward.md    | 19 +++++++++++++++----
 3 files changed, 24 insertions(+), 8 deletions(-)

diff --git a/website/docs/getting-started/faq.md b/website/docs/getting-started/faq.md
index c17165e6..032e5a2b 100644
--- a/website/docs/getting-started/faq.md
+++ b/website/docs/getting-started/faq.md
@@ -36,8 +36,8 @@ Q: How can I contribute to Meshtastic?
 Q: Where do I purchase the device hardware?
 * Answer TBD
 
-Q: I have my hardware. How do I install the firmware?
-* Answer TBD
+Q: I have my hardware. How do I install the firmware and any required drivers?
+* See: https://meshtastic.org/docs/getting-started/flashing-esp32
 
 Q: How do I update the firmware to the latest version?
 * Answer TBD
@@ -48,8 +48,11 @@ Q: My device has gone to sleep. Are received messages lost?
 Q: My device has gone to sleep and I can't send any messages.
 * Once the node wakes up from sleep, your phone will relay any delayed messages through your node and to the mesh network. Give it a few minutes and it'll do the right thing.
 
-Q: How do I turn on / off an esp32 tbeam based device?
-* Answer TBD
+Q: How do I turn off an esp32 tbeam based device?
+* Hold down the middle button for about 10 seconds.
+
+Q: How do I turn on an esp32 tbeam based device?
+* Push the power button for about 1 second.
 
 Q: How can I tell the device not to sleep?
 * Android instructions see: [Android Usage](https://meshtastic.org/docs/software/android/android-usage#configuration-options)
diff --git a/website/docs/getting-started/flashing-esp32.md b/website/docs/getting-started/flashing-esp32.md
index 9f461372..40d029c2 100644
--- a/website/docs/getting-started/flashing-esp32.md
+++ b/website/docs/getting-started/flashing-esp32.md
@@ -13,6 +13,8 @@ import TabItem from '@theme/TabItem';
 Plug your device into your computer using a USB cable and then do the following:
 :::important
 You may need to install a driver from Silicon Labs for the [CP210X USB to UART bridge](https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers)
+
+Some newer boards may require the drivers for the [CH9102 USB to UART bridge](https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/drivers/CH9102_VCP_SER_Windows.exe) on Windows 7.
 :::
 
 <Tabs
diff --git a/website/docs/software/plugins/store-forward.md b/website/docs/software/plugins/store-forward.md
index 701d30d0..7304c6d9 100644
--- a/website/docs/software/plugins/store-forward.md
+++ b/website/docs/software/plugins/store-forward.md
@@ -79,14 +79,25 @@ Not necessarily in this order:
 
 * Be able to identify if you're within range of a router.
 
-* Be able to specify the HOP MAX to reduce airtime.
+* Be able to specify the HOP MAX to reduce airtime. Is this necessary?
 
-* Restrict operation of S&F on the slow channel configurations.     
+* Restrict operation of S&F on the slow channel configurations.
 
-*/
+* Create a tx queue to prevent the history from being modified in flight.
+
+* Only allow n-number of requests to the router at any one time.
+
+* Set number of max messages from the history.
+
+* Calculate a new channel with 250mhz bandwidth and ~1.5kbit.
 
 *** Done
 
+* Disable ACK. If the router is within range, so is the requester.
+
 * Currently the way we allocate messages in the device code is super inefficient. It always allocates the worst case message size. Really we should dynamically allocate just the # of bytes we need. This would allow many more MeshPackets to be kept in RAM.
 
-* Allow max history to be defined by radioConfig.preferences.store_forward_plugin_records
\ No newline at end of file
+* Allow max history to be defined by radioConfig.preferences.store_forward_plugin_records
+
+* Add a starting to send / finished sending message
+