aboutsummaryrefslogtreecommitdiff
path: root/src/machine.tex
diff options
context:
space:
mode:
Diffstat (limited to 'src/machine.tex')
-rw-r--r--src/machine.tex8
1 files changed, 2 insertions, 6 deletions
diff --git a/src/machine.tex b/src/machine.tex
index 25ce958..c43a9b8 100644
--- a/src/machine.tex
+++ b/src/machine.tex
@@ -278,8 +278,7 @@ microarchitectures.
The convention adopted within the following Implementation field can
be used to segregate branches of the same architecture design,
including by organization. The {\tt misa} register also helps
-distinguish different variants of a design, as does the configuration
-string if present.
+distinguish different variants of a design.
\end{commentary}
\subsection{Machine Implementation ID Register {\tt mimpid}}
@@ -2377,10 +2376,7 @@ devices or to correctly configure other hardware components that
access memory, such as DMA engines. As PMAs are tightly tied to a
given physical platform's organization, many details are inherently
platform-specific, as is the means by which software can learn the PMA
-values for a platform. The configuration string
-(Chapter~\ref{cfgstr}) can encode PMAs for on-chip devices and might
-also describe on-chip controllers for off-chip buses that can be
-dynamically interrogated to discover attached device PMAs. Some
+values for a platform. Some
devices, particularly legacy buses, do not support discovery of PMAs
and so will give error responses or time out if an unsupported access
is attempted. Typically, platform-specific machine-mode code will