From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date: Thu, 26 Apr 2018 07:19:38 +0000 (+0100)
Subject: start filling in
X-Git-Tag: convert-csv-opcode-to-binary~5503
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=d9e2513bac57717ad4f741f9045184e3c910b54c;hp=25ede9c3cf35e7f58f92bd02f90e3cd3ffeab193;p=libreriscv.git

start filling in
---

diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn
index d0ed7ad6f..64fc5cb0c 100644
--- a/isa_conflict_resolution.mdwn
+++ b/isa_conflict_resolution.mdwn
@@ -13,6 +13,14 @@ within the current RISC-V Specification to transition to improved versions
 of the standard, regardless of whether the fixes are absolutely critical
 show-stoppers or whether they are just keeping the standard up-to-date (2).
 
+With no transition path there is guaranteed to be tension and conflict
+within the RISC-V Community over whether revisions should be made:
+should existing legacy designs be prioritised, mutually-exclusively over
+future designs (and what happens during the transition period is absolute
+chaos).  If several overlapping revisions are required that have not
+yet transitioned out of use (which could take well over two decades to
+occur) the situation becomes disastrous for the credibility of RISC-V.
+
 It was also pointed out that Compliance is an extremely important factor
 to take into consideration, and that Custom Extensions (as being optional)
 effectively fall entirely outside of the Compliance Testing.  At this