From 18183704ec836889e18a09ac420a48c6b30e3fe8 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 10:47:26 +0100 Subject: [PATCH] start filling in --- isa_conflict_resolution.mdwn | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index 746928ff1..36a29009d 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -148,7 +148,8 @@ problem, therefore there isn't a problem". The logical errors in this argument were quickly enumerated: namely that the RISC-V Foundation is not in control of the uses to which RISC-V is put, such that public global conflicts in binary-encoding are a hundred -percent guaranteed to occur, and a hundred percent guaranteed to occur in +percent guaranteed to occur (*outside* of the control and remit of the +RISC-V Foundation), and a hundred percent guaranteed to occur in *commodity* hardware where Debian, Fedora, SUSE and other distros will be hardest hit by the resultant chaos, and that will just be the more "visible" aspect of the underlying problem. -- 2.30.2