add alu_fsm.py source link

diff --git a/Documentation/gtkwave_tutorial.mdwn b/Documentation/gtkwave_tutorial.mdwn
index a45966c551420981e52447cd957a1f0e05e99753..f9209c3f6f1b77cb2ae6f919b0dd8b1f4e34408b 100644 (file)
--- a/Documentation/gtkwave_tutorial.mdwn
+++ b/Documentation/gtkwave_tutorial.mdwn
@@ -1,9 +1,10 @@
 # GTKWave improvements
 
-(Originally at <http://lists.libre-soc.org/pipermail/libre-soc-dev/2020-August/000146.html>)
+* (Originally at <http://lists.libre-soc.org/pipermail/libre-soc-dev/2020-August/000146.html>)
+* [alu_fsm.py source](https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/experiment/alu_fsm.py;h=9668535aedc8e507212906baf679dc37484b8e8d;hb=1d4fa2db3d660510ebeceb650188c6fcf3127fd4#l209)
 
 Lately, I've been investigating about generating better GTKWave "save"
-files (*.gtkw), from Python. The goal is to ease analysis of traces
+files (\*.gtkw), from Python. The goal is to ease analysis of traces
 generated by unit-tests, and at the same time to better understand the
 inner working of modules, for which we are writing such tests.