From 07689e1e0cc1bc61c507f87d971c2507cbcf65a5 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Thu, 26 Apr 2018 11:57:19 +0100 Subject: [PATCH] comments and references --- isa_conflict_resolution.mdwn | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn index 3476b0567..31b8fd2c0 100644 --- a/isa_conflict_resolution.mdwn +++ b/isa_conflict_resolution.mdwn @@ -326,16 +326,18 @@ being worthwhile in its own right, and standing on its own merits and thus definitely worthwhile pursuing, it is non-trivial and much more invasive than the mvendor/march-id WARL concept. -# Discussion and analysis +# Comments, Discussion and analysis -TBD +TBD: placeholder as of 26apr2018 -# Conclusion +# Summary and Conclusion In the early sections (those in the category "no action") it was established in each case that the problem is not solved. Avoidance of responsibility, or conflation of "not our problem" with "no problem" does not make "problem" -go away. +go away. Even "making it the Fabless Semiconductor's problem" resulted +in a chip being *more costly to engineer and maintain*... without actually +fixing the problem. The first idea considered which could fix the problem was to just use the pre-existing MISA CSR, however this was determined not to have @@ -439,3 +441,8 @@ The following conversation exerpts are taken from the ISA-dev discussion > it is implementing. It will test nothing in the custom extension space, > and doesn't monitor or care what is in that space. +# References + +* +* + -- 2.30.2