Skip to content

Commit ecc1efe

Browse files
committed
doc: fix URLs
1 parent 3ba41c0 commit ecc1efe

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

doc/introduction.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Background
1212

1313
Even though the Milkymist system-on-chip [mm]_ had many successes, it suffers from several limitations stemming from its implementation in manually written Verilog HDL:
1414

15-
.. [mm] http://m-labs.hk
15+
.. [mm] https://m-labs.hk/gateware/m1/
1616
1717
#. The "event-driven" paradigm of today's dominant hardware descriptions languages (Verilog and VHDL, collectively referred to as "V*HDL" in the rest of this document) is often too general. Today's FPGA architectures are optimized for the implementation of fully synchronous circuits. This means that the bulk of the code for an efficient FPGA design falls into three categories:
1818

@@ -40,8 +40,8 @@ Even though the Milkymist system-on-chip [mm]_ had many successes, it suffers fr
4040
#. Many hardware acceleration problems can fit into the dataflow programming model. Manual dataflow implementation in V*HDL has, again, a lot of redundancy and potential for human errors. See the Milkymist texture mapping unit [mthesis]_ [mxcell]_ for an example of this. The amount of detail to deal with manually also makes the design space exploration difficult, and therefore hinders the design of efficient architectures.
4141
#. Pre-computation of values, such as filter coefficients for DSP or even simply trigonometric tables, must often be done using external tools whose results are copy-and-pasted (in the best case, automatically) into the V*HDL source.
4242

43-
.. [mthesis] http://m-labs.hk/thesis/thesis.pdf
44-
.. [mxcell] http://www.xilinx.com/publications/archives/xcell/Xcell77.pdf p30-35
43+
.. [mthesis] https://m-labs.hk/thesis/thesis.pdf
44+
.. [mxcell] https://www.xilinx.com/publications/archives/xcell/Xcell77.pdf p30-35
4545
4646
Enter Migen, a Python toolbox for building complex digital hardware. We could have designed a brand new programming language, but that would have been reinventing the wheel instead of being able to benefit from Python's rich features and immense library. The price to pay is a slightly cluttered syntax at times when writing descriptions in FHDL, but we believe this is totally acceptable, particularly when compared to VHDL ;-)
4747

@@ -58,16 +58,16 @@ Installing Migen
5858
Either run the ``setup.py`` installation script or simply set ``PYTHONPATH`` to the root of the source directory.
5959

6060
If you wish to contribute patches, the suggest way to install is;
61-
#. Clone from the git repository at http://github.com/m-labs/migen
61+
#. Clone from the git repository at https://github.com/m-labs/migen
6262
#. Install using ``python3 ./setup.py develop --user``
6363
#. Edit the code in your git checkout.
6464

6565
Alternative install methods
6666
===========================
6767

6868
* Migen is available for the Anaconda Python distribution. The package can be found at at https://anaconda.org/m-labs/migen
69-
* Migen can be referenced in a requirements.txt file (used for ``pip install -r requirements.txt``) via ``-e git+http://github.com/m-labs/migen.git#egg=migen``. See the pip documentation for more information.
69+
* Migen can be referenced in a requirements.txt file (used for ``pip install -r requirements.txt``) via ``-e git+https://github.com/m-labs/migen.git#egg=migen``. See the pip documentation for more information.
7070

7171
Feedback
7272
********
73-
Feedback concerning Migen or this manual should be sent to the M-Labs developers' mailing list ``devel`` on lists.m-labs.hk.
73+
Feedback concerning Migen or this manual should be sent to the M-Labs forum at https://forum.m-labs.hk or in GitHub issues.

0 commit comments

Comments
 (0)