From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date: Mon, 30 Apr 2018 09:58:51 +0000 (+0100)
Subject: clarify
X-Git-Tag: convert-csv-opcode-to-binary~5416
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=1365f26fbdaa04dada847cc6578cb31f72dd8e0e;p=libreriscv.git

clarify
---

diff --git a/isa_conflict_resolution/mvendor_march_warl.mdwn b/isa_conflict_resolution/mvendor_march_warl.mdwn
index 2cb1ea348..f19179818 100644
--- a/isa_conflict_resolution/mvendor_march_warl.mdwn
+++ b/isa_conflict_resolution/mvendor_march_warl.mdwn
@@ -68,7 +68,8 @@ to not be permitted to receive RISC-V Certification Compliance.
 
 How such foreign architectures would switch back to RISC-V when the foreign
 architecture does not support the concept of mvendorid-marchid is out of
-scope and left to implementors.
+scope and left to implementors to define and implement equivalent
+functionality.
 
 ## Implementation
 
@@ -153,3 +154,8 @@ The clear separation which mutually-exclusively redirects encodings based
 on which mvendorid-marchid tuple is currently active clearly meets that
 requirement.
 
+# Questions to be resolved
+
+* Can the declaration (meaning) of read-only be expanded to cover
+  any number of (non-conflicting) Custom Extensions?  What are the
+  implications of doing so?