diff options
| author | Andrew Waterman <andrew@sifive.com> | 2018-01-23 11:50:14 -0800 |
|---|---|---|
| committer | Andrew Waterman <andrew@sifive.com> | 2018-01-23 11:50:36 -0800 |
| commit | 80c6c88873d1297ad47b77179c4001d0896c9836 (patch) | |
| tree | 02e87d3e7824f765dfb233f1f04535ddcb4ba22c /src/machine.tex | |
| parent | 7aa8bdba807c44df40a073934458726b3be49fdd (diff) | |
| download | riscv-isa-manual-80c6c88873d1297ad47b77179c4001d0896c9836.zip riscv-isa-manual-80c6c88873d1297ad47b77179c4001d0896c9836.tar.gz riscv-isa-manual-80c6c88873d1297ad47b77179c4001d0896c9836.tar.bz2 | |
Use y instead of a in PMP addresses
So they don't get confused for hexadecimal numbers.
Diffstat (limited to 'src/machine.tex')
| -rw-r--r-- | src/machine.tex | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/src/machine.tex b/src/machine.tex index d281b3b..c3f5bc4 100644 --- a/src/machine.tex +++ b/src/machine.tex @@ -2762,13 +2762,13 @@ to encode the size of the range, as shown in Table~\ref{pmpcfg-napot}. \hline \tt pmpaddr & {\tt pmpcfg}.A & Match type and size \\ \hline - \tt aaaa...aaaa & NA4 & 4-byte NAPOT range \\ - \tt aaaa...aaa0 & NAPOT & 8-byte NAPOT range \\ - \tt aaaa...aa01 & NAPOT & 16-byte NAPOT range \\ - \tt aaaa...a011 & NAPOT & 32-byte NAPOT range \\ + \tt yyyy...yyyy & NA4 & 4-byte NAPOT range \\ + \tt yyyy...yyy0 & NAPOT & 8-byte NAPOT range \\ + \tt yyyy...yy01 & NAPOT & 16-byte NAPOT range \\ + \tt yyyy...y011 & NAPOT & 32-byte NAPOT range \\ \multicolumn{1}{|c|}{\ldots} & \ldots & \multicolumn{1}{|c|}{\ldots} \\ - \tt aa01...1111 & NAPOT & $2^{XLEN}$-byte NAPOT range \\ - \tt a011...1111 & NAPOT & $2^{XLEN+1}$-byte NAPOT range \\ + \tt yy01...1111 & NAPOT & $2^{XLEN}$-byte NAPOT range \\ + \tt y011...1111 & NAPOT & $2^{XLEN+1}$-byte NAPOT range \\ \tt 0111...1111 & NAPOT & $2^{XLEN+2}$-byte NAPOT range \\ \tt 1111...1111 & NAPOT & {\em Reserved} \\ \hline @@ -2781,9 +2781,9 @@ to encode the size of the range, as shown in Table~\ref{pmpcfg-napot}. If TOR is selected, the associated address register forms the top of the address range, and the preceding PMP address register forms the bottom of the address range. If PMP entry $i$'s A field is set to TOR, the entry matches -any address $a$ such that ${\tt pmpaddr}_{i-1}\leq a < {\tt pmpaddr}_i$. If +any address $y$ such that ${\tt pmpaddr}_{i-1}\leq y < {\tt pmpaddr}_i$. If PMP entry 0's A field is set to TOR, zero is used for the lower bound, and so -it matches any address $a < {\tt pmpaddr}_0$. +it matches any address $y < {\tt pmpaddr}_0$. \subsubsection*{Locking and Privilege Mode} |