Worked example pictures

diff --git a/openpower/sv/cookbook/inner_product_worked_example.jpg b/openpower/sv/cookbook/inner_product_worked_example.jpg
new file mode 100644 (file)
index 0000000..3a90701
Binary files /dev/null and b/openpower/sv/cookbook/inner_product_worked_example.jpg differ

diff --git a/openpower/sv/cookbook/outer_product_worked_example.jpg b/openpower/sv/cookbook/outer_product_worked_example.jpg
new file mode 100644 (file)
index 0000000..cd7b9b2
Binary files /dev/null and b/openpower/sv/cookbook/outer_product_worked_example.jpg differ

diff --git a/openpower/sv/cookbook/remap_matrix.mdwn b/openpower/sv/cookbook/remap_matrix.mdwn
index 5defbcdd07b0235e96fcd9f1a49208b98e534e62..ad876e51da7a75d4851fc831301a61e1d043c5d4 100644 (file)
--- a/openpower/sv/cookbook/remap_matrix.mdwn
+++ b/openpower/sv/cookbook/remap_matrix.mdwn
@@ -124,6 +124,9 @@ Index list:
     |   5   |   5   |   3   |
 ```
 
+Worked example broken down into individual multiply-add accumulates:
+
+[[!img outer_product_worked_example.jpg size="600x ]]
 
 The issue with this algorithm is that the result matrix element is the same
 for three consecutive operations, and where each element is stored in CPU
@@ -163,6 +166,10 @@ Index list:
     |   5   |   5   |   3   |
 ```
 
+Worked example for inner product:
+
+[[!img inner_product_worked_example.jpg size="600x ]]
+
 The index for the result matrix changes with every operation, and thus the
 consecutive multiply-add instruction doesn't depend on the previous write
 register.