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