FPGA/myhdl
1
0
Fork 0
mirror of https://github.com/myhdl/myhdl.git synced 2025-01-24 21:52:56 +08:00
Code Issues Projects Releases Wiki Activity

Proof read

Browse Source
This commit is contained in:
jand 2003-03-07 09:17:35 +00:00
parent d4bc61a01f
commit 8c680765ed
2 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/informal.tex
View File

@ -434,10 +434,10 @@ We use the bus functional procedure call as a clause in the
\code{yield} statement: using a generator as a clause. Although this is
a more dynamic usage than in the previous cases, the meaning is
actually very similar. When the calling generator \code{stimulus()}
encounters the \code{yield} statement, the Simulator suspends its
execution and looks to the clause to know when it should resume. In
this case, it \dfn{spawns} the generator \code{rs232_tx(tx, txData)},
and resumes the caller when the spawned generator returns.
encounters the \code{yield} statement, it suspends exectution, and the
clause specifieds when it should resume. In this case, the generator
\code{rs232_tx(tx, txData)} is \dfn{forked}, and the caller resumes
when the forked generator returns.
When simulating this, we get:
@ -532,7 +532,7 @@ def test():
\end{verbatim}
Both spawned generators will run concurrently, and the calling
Both forked generators will run concurrently, and the calling
generator will resume as soon as one of them finishes (which will be
the transmitter in this case). The simulation output shows how
the UART procedures run in lockstep:
@ -598,10 +598,10 @@ StopSimulation: RX time out error
\end{verbatim}
Recall that the calling generator resumes as soon as one of the
spawned generators returns. In the previous cases, this is just fine,
forked generators returns. In the previous cases, this is just fine,
as the transmitter and receiver generators run in lockstep. However,
it may be desirable to resume the caller only when \emph{all} of the
spawned generators have finished. For example, suppose that we want to
forked generators have finished. For example, suppose that we want to
characterize the robustness of the transmitter and receiver design to
bit duration differences. We can adapt our test bench as follows, to
run the transmitter at a faster rate:

6
doc/reference.tex
View File

@ -110,9 +110,9 @@ generator is triggered.
\begin{datadesc}{GeneratorType}
\myhdl\ generators can itself be used as trigger objects.
This corresponds to spawning a new generator, while the original
This corresponds to forking a new generator, while the original
generator waits for it to complete. In other words, the original
generator is triggered when the spawned generator completes.
generator is triggered when the forked generator completes.
\end{datadesc}
In addition, as a special case, the Python \code{None} object can be
@ -122,7 +122,7 @@ present in a \code{yield} statement:
This is the do-nothing trigger object. The generator immediately
resumes, as if no \code{yield} statement were present. This can be
useful if the \code{yield} statement also has generator clauses: those
generators are spawned, while the original generator resumes
generators are forked, while the original generator resumes
immediately.
\end{datadesc}