(no commit message)

diff --git a/nlnet_2019_amdvlk_port/questions.mdwn b/nlnet_2019_amdvlk_port/questions.mdwn
index 8e0e262002348e0eee50de47be9c29dbd7fdaec8..64dc148bab533bc3f52e6bd512bbabbbcc5bf9f0 100644 (file)
--- a/nlnet_2019_amdvlk_port/questions.mdwn
+++ b/nlnet_2019_amdvlk_port/questions.mdwn
@@ -17,3 +17,12 @@ to the effort?
 
 How do you see future synchronisation with the evolving AMD code,
 assuming this is still actively developed?
+
+# Answer
+
+* the development strategy is iterative (described previously and used right across the board: simulation first, with improvements).  the improvements - the addition of extra instructions and extra iterative cycles - continue as long as funding is available, always with the "previous version" being stable and useable.
+* no, it will not be an "isolated effort".  TODO: jacob's help
+* no, we are not critically dependent on Mesa or AMD.
+* note that we haven't decided yet whether to go with AMDVLK or RADV.  RADV unfortunately was developed by David Airlie, who caused massive problems for Luc Verhagen.
+* upstreaming will come "over time" as part of wider adoption.
+* TODO: describe that AMDVLK is a port of the windows driver