mirror of
https://github.com/YosysHQ/yosys
synced 2025-06-06 14:13:23 +00:00
docs: restructuring images directory
see also previous commit Also updates `scripting_intro.rst` to use literal includes, and uses individual image outputs to avoid the intermediary `.tex` file to join them all.
This commit is contained in:
parent
dbc38d72cf
commit
b6e61c16b1
44 changed files with 131 additions and 237 deletions
|
@ -58,7 +58,7 @@ provides.
|
|||
This document will focus on the much simpler version of RTLIL left after the
|
||||
commands :cmd:ref:`proc` and :cmd:ref:`memory` (or ``memory -nomap``):
|
||||
|
||||
.. figure:: /_images/simplified_rtlil.*
|
||||
.. figure:: /_images/internals/simplified_rtlil.*
|
||||
:class: width-helper
|
||||
:name: fig:Simplified_RTLIL
|
||||
|
||||
|
|
|
@ -9,7 +9,7 @@ a predetermined order, each consuming the data generated by the last subsystem
|
|||
and generating the data for the next subsystem (see :numref:`Fig. %s
|
||||
<fig:approach_flow>`).
|
||||
|
||||
.. figure:: /_images/approach_flow.*
|
||||
.. figure:: /_images/internals/approach_flow.*
|
||||
:class: width-helper
|
||||
:name: fig:approach_flow
|
||||
|
||||
|
|
|
@ -40,7 +40,7 @@ possible it is key that (1) all passes operate on the same data structure
|
|||
(RTLIL) and (2) that this data structure is powerful enough to represent the
|
||||
design in different stages of the synthesis.
|
||||
|
||||
.. figure:: /_images/overview_flow.*
|
||||
.. figure:: /_images/internals/overview_flow.*
|
||||
:class: width-helper
|
||||
:name: fig:Overview_flow
|
||||
|
||||
|
|
|
@ -9,7 +9,7 @@ abstract syntax tree (AST) representation of the input. This AST representation
|
|||
is then passed to the AST frontend that converts it to RTLIL data, as
|
||||
illustrated in :numref:`Fig. %s <fig:Verilog_flow>`.
|
||||
|
||||
.. figure:: /_images/verilog_flow.*
|
||||
.. figure:: /_images/internals/verilog_flow.*
|
||||
:class: width-helper
|
||||
:name: fig:Verilog_flow
|
||||
|
||||
|
|
|
@ -23,7 +23,7 @@ pass is reading an auxiliary Verilog file such as a cell library, it might
|
|||
create an additional ``RTLIL::Design`` object and call the Verilog frontend with
|
||||
this other object to parse the cell library.
|
||||
|
||||
.. figure:: /_images/overview_rtlil.*
|
||||
.. figure:: /_images/internals/overview_rtlil.*
|
||||
:class: width-helper
|
||||
:name: fig:Overview_RTLIL
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue