Continued adding initial skeleton markdown content

Author: azonenberg

getinvolved.md

@@ -1,3 +1,10 @@
 # Get Involved
 
+Want to contribute to the project? We suggest joining the developer chat, which may be accessed via your choice of IRC or Discord (both channels are bridged so you can talk to everyone from either protocol).
 
+* IRC: \#scopehal on irc.libera.chat
+* Discord: \#scopehal on 1bitsquared https://discord.gg/URuN2BuGwG
+
+This is the primary mechanism for active developers to discuss features they're working on, help each other out, and coordinate the overall direction of the project.
+
+We also host developer meetings on Zoom, typically about once per month. Connection and scheduling information is shared in the chat channel.

hardware.md

@@ -1,6 +1,6 @@
-# Overview
+# Supported Hardware
 
-This is a brief list of hardware known to work with by libscopehal, sorted by manufacturer. Similar models may work as well although correct functionality is not guaranteed. We'd love to hear results (successful or otherwise) of testing with instruments not listed here.
+This is a brief list of hardware known to work with by libscopehal and ngscopeclient, sorted by manufacturer. Similar models may work as well although correct functionality is not guaranteed. We'd love to hear results (successful or otherwise) of testing with instruments not listed here.
 
 For full details on which features are or are not supported by particular drivers, known issues, etc. please see the appropriate section of the manual.
 

index.md

@@ -1 +1 @@
-
+# Welcome

libscopehal.md

@@ -0,0 +1 @@
+# What is libscopehal?

multiscope.md

@@ -0,0 +1,13 @@
+# Multi-scope support
+
+Ngscopeclient allows a single session to connect to arbitrarily many oscilloscopes simultaneously. These instruments can be fully independent of each other (triggering with no relationship to the others) or grouped into "trigger groups", via a cross-trigger sync cable, allowing several instruments to trigger in lock-step.
+
+Any number of oscilloscopes, of any supported make or model, may be combined in the same trigger group. Sample rates need not be the same, and the horizontal positions of each instrument within a group may be adjusted independently. This allows complex analytical setups for study of behavior across varying time scales:
+
+* Use a high speed oscilloscope to identify packets or signal integrity issues in a gigabit serial signal, then trigger a low-speed instrument recording tens or hundreds of ms of activity on status GPIOs, MDIO or I2C buses, etc. before and after the high speed events
+* Combine multiple instruments to capture data on more channels than a single instrument can support
+* Use two or more instruments to capture cause-and-effect pairs on different channels separated by arbitrarily long time periods, while displaying on a single timeline
+
+An automated deskew wizard allows the cross-trigger path delay within a trigger group to be measured and calibrated out, so that waveforms from all oscilloscopes in the group will line up correctly on the timeline.
+
+Protocol decodes, math functions, and filter blocks can work across inputs from multiple instruments. Most math functions require their inputs to be sampled at the same rate, so you may need to use a resampling block if the instruments are not configured identically. Most protocol decode blocks can work with inputs of different sample rates without issue as long as the deskew calibration has been performed.

ngscopeclient.md

@@ -0,0 +1 @@
+# What is ngscopeclient?

protocol-analysis.md

@@ -0,0 +1 @@
+# Protocol Analysis

support.md

@@ -0,0 +1,2 @@
+# Support
+