mirror of https://github.com/VLSIDA/OpenRAM.git
Move hints to FAQ and link to documentation
This commit is contained in:
parent
fb66e37ac0
commit
74a1e21485
|
|
@ -194,12 +194,10 @@ You can view the .out file to see what the output of a test is in either case.
|
|||
|
||||
# Further Help
|
||||
|
||||
+ [Additional hints](./HINTS.md)
|
||||
+ [Documentation][documentation]
|
||||
+ [OpenRAM Slack Workspace][Slack]
|
||||
+ [OpenRAM Users Group][user-group] ([subscribe here][user-group-subscribe])
|
||||
+ [OpenRAM Developers Group][dev-group] ([subscribe here][dev-group-subscribe])
|
||||
+ <a rel="me" href="https://fosstodon.org/@mrg">@mrg@fostodon.org</a>
|
||||
|
||||
# License
|
||||
|
||||
|
|
@ -223,9 +221,9 @@ If I forgot to add you, please let me know!
|
|||
|
||||
[Github issues]: https://github.com/VLSIDA/OpenRAM/issues
|
||||
[Github pull request]: https://github.com/VLSIDA/OpenRAM/pulls
|
||||
[Github project]: https://github.com/VLSIDA/OpenRAM
|
||||
[Github project]: https://github.com/VLSIDA/OpenRAM
|
||||
|
||||
[documentation]: https://docs.google.com/presentation/d/10InGB33N51I6oBHnqpU7_w9DXlx-qe9zdrlco2Yc5co/edit?usp=sharing
|
||||
[documentation]: documentation/docs/source/index.md
|
||||
[dev-group]: mailto:openram-dev-group@ucsc.edu
|
||||
[user-group]: mailto:openram-user-group@ucsc.edu
|
||||
[dev-group-subscribe]: mailto:openram-dev-group+subscribe@ucsc.edu
|
||||
|
|
|
|||
|
|
@ -1,3 +1,5 @@
|
|||
### [Go Back](./index.md#directory)
|
||||
|
||||
# Debugging
|
||||
|
||||
When OpenRAM runs, it puts files in a temporary directory that is
|
||||
|
|
@ -24,6 +24,7 @@ These pages provide the documentation of OpenRAM. You can use the links below to
|
|||
16. [Routing](./routing.md#go-back)
|
||||
17. [Characterization](./characterization.md#go-back)
|
||||
18. [Results](./results.md#go-back)
|
||||
19. [FAQ](./FAQ.md#go-back)
|
||||
|
||||
|
||||
|
||||
|
|
@ -101,4 +102,4 @@ These pages provide the documentation of OpenRAM. You can use the links below to
|
|||
* Verification wrapper scripts
|
||||
* Uses a wrapper interface with DRC and LVS tools that allow flexibility
|
||||
* DRC and LVS can be performed at all levels of the design hierarchy to enhance bug tracking.
|
||||
* DRC and LVS can be disabled completely for improved run-time or if licenses are not available.
|
||||
* DRC and LVS can be disabled completely for improved run-time or if licenses are not available.
|
||||
|
|
|
|||
Loading…
Reference in New Issue