more clarification on ranges

diff --git a/openpower/sv/svp64.mdwn b/openpower/sv/svp64.mdwn
index dae7e7b290cd57365b621e00aabe3ce35bfa6fd9..d05e2f5bad50d27ac3f1e6837bfd795b820efb30 100644 (file)
--- a/openpower/sv/svp64.mdwn
+++ b/openpower/sv/svp64.mdwn
@@ -592,14 +592,19 @@ If EXTRA2 is zero will map to
 | 10       | Vector | `r0-r124`/4 | `RA 0b00`      |
 | 11       | Vector | `r2-r126`/4 | `RA 0b10`   |
 
-Note that unlike in EXTRA3, in EXTRA2 the GPR Vectors may only start from
-`r0, r2, r4, r6, r8` and likewise FPR Vectors as there is insufficient
-bits to cover the full range.
+**Note that unlike in EXTRA3, in EXTRA2**:
+
+* the GPR Vectors may only start from
+  `r0, r2, r4, r6, r8` and likewise FPR Vectors.
+* the GPR Scalars may only go from `r0, r1, r2.. r63` and likewise FPR Scalars.
+
+as there is insufficient bits to cover the full range.
 
 ## CR Field EXTRA3
 
 CR Field encoding is essentially the same but made more complex due to CRs being bit-based.  See [[svp64/appendix]] for explanation and pseudocode.
-Note that Vectors may only start from `CR0, CR4, CR8, CR12, CR16`...
+Note that Vectors may only start from `CR0, CR4, CR8, CR12, CR16, CR20`...
+and Scalars may only go from `CR0, CR1, ... CR31`
 
 Encoding shown MSB down to LSB