(no commit message)

[libreriscv.git] / index.mdwn

diff --git a/index.mdwn b/index.mdwn
index 671538ab4b512a123f4e872e47f7ee4bbd20ad2c..f7d1345c275230c9b52068c93ccc068ad41cfb92 100644 (file)
--- a/index.mdwn
+++ b/index.mdwn
@@ -5,7 +5,7 @@
 
   <p>A chip with lots of peripherals. And a VPU.  And a 3D GPU...</p>
 
 
   <p>A chip with lots of peripherals. And a VPU.  And a 3D GPU...</p>
 

-  <p>Oh and here, have the <a href="http://git.libre-riscv.org">source code</a>...</p>
+  <p>Oh and here, have the <a href="http://git.libre-soc.org">source code</a>...</p>

 </blockquote>
   <hr class="my-4">
 
 </blockquote>
   <hr class="my-4">
 


@@ -81,18 +81,21 @@ below.  If there is anything else,
 just get in touch on the list, there is plenty to do.
 
 1. First, join the
 just get in touch on the list, there is plenty to do.
 
 1. First, join the

-  [mailing list](http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev),
-  introduce yourself (people will happily say "hello" back"). Read through
-  [recent posts](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/)
-  and the [[charter]], and let everyone know, on the list that you're
-  happy with it and agree to it.
+  [mailing list](http://lists.libre-soc.org/mailman/listinfo/libre-soc-dev),
+  introduce yourself (people will happily say "hello" back") and
+  the Freenode IRC channel
+  [#libre-soc](https://libre-soc.org/irclog/latest.log.html).
+  Read through
+  [recent posts](http://lists.libre-soc.org/pipermail/libre-soc-dev/)
+  and the [[charter]], ask questions if you have any and let everyone know,
+  on the list that you're happy with it and agree to it.

 2. The next thing you should do is read through the
 2. The next thing you should do is read through the

-  [bugs list](http://bugs.libre-riscv.org) and
+  [bugs list](http://bugs.libre-soc.org) and

   see if there are any bugs that pique your interest.
   A fascinating way to do that is to view the
   [dependency graph](https://bugs.libre-soc.org/showdependencygraph.cgi?id=1&display=web&rankdir=LR)
 3. After that, go ahead and take a look at the
   see if there are any bugs that pique your interest.
   A fascinating way to do that is to view the
   [dependency graph](https://bugs.libre-soc.org/showdependencygraph.cgi?id=1&display=web&rankdir=LR)
 3. After that, go ahead and take a look at the

-   [git repositories](https://git.libre-riscv.org).
+   [git repositories](https://git.libre-soc.org).

 4. If you plan to do HDL work, you should familiarize yourself with our
   [[HDL_workflow]].  If you would like to help with the ASIC layout,
   see [[HDL_workflow/coriolis2]]
 4. If you plan to do HDL work, you should familiarize yourself with our
   [[HDL_workflow]].  If you would like to help with the ASIC layout,
   see [[HDL_workflow/coriolis2]]


@@ -116,9 +119,9 @@ Here is an example process of how to play with the soc code:
     source ~/.virtualenvs/libresoc/bin/activate
     
     cd ~; mkdir libresoc; cd libresoc
     source ~/.virtualenvs/libresoc/bin/activate
     
     cd ~; mkdir libresoc; cd libresoc

-    git clone https://git.libre-riscv.org/git/nmutil.git
-    git clone https://git.libre-riscv.org/git/ieee754fpu.git
-    git clone https://git.libre-riscv.org/git/soc.git
+    git clone https://git.libre-soc.org/git/nmutil.git
+    git clone https://git.libre-soc.org/git/ieee754fpu.git
+    git clone https://git.libre-soc.org/git/soc.git

     
     cd nmutil; make install; cd ..
     cd ieee754fpu; make install; cd ..
     
     cd nmutil; make install; cd ..
     cd ieee754fpu; make install; cd ..


@@ -160,4 +163,7 @@ accelerated opcodes (all of which SwiftShader lacks)
 Also, individuals with experience in formal mathematical verification
 are quite welcome.
 
 Also, individuals with experience in formal mathematical verification
 are quite welcome.
 

-# [Documentation](Documentation/SOC/index)
+# Documentation
+
+ - [Source Code](/Documentation/index)
+ - [Architecture](3d_gpu/architecture)