(no commit message)

diff --git a/openpower/ISA_WG/Board_letter_26mar2021.mdwn b/openpower/ISA_WG/Board_letter_26mar2021.mdwn
index de7369ac6a77a1c027fb2f39884940c144eb43d0..85c904d1a8d8e71178af52d4b766ccf3ed1e4384 100644 (file)
--- a/openpower/ISA_WG/Board_letter_26mar2021.mdwn
+++ b/openpower/ISA_WG/Board_letter_26mar2021.mdwn
@@ -43,6 +43,14 @@ The advice in the PowerISA v3.0C document therefore *require* us to contact the
 
 In speaking verbally and informally with various people (Toshaan, Paul and Hugh) we have pieced together the way that the OpenPOWER Foundation ISA Workgroup is to be set up, and we have become aware that there may be a mis-match here caused by "otherwise normally expected" provenance of ISA proposals which, from what we can gather, is being built-in to the ISA WG's by-laws.
 
-From what we understand, there are two things: firstly that individuals with no affiliation (to a Company or Academic Institution) would be prevented from tabling arbitrary ISA extensions (without a sponsor, that is).  Given that the OPF ISA WG has to act entirely fairly i.e. in a non-discriminatory fashion towards all proposals, yet also take into account the huge burden of time and responsibility that results in perpetuity from any such inclusion it is a reasonable balance, 
+From what we understand, individuals with no affiliation (to a Company or Academic Institution) would be prevented from tabling arbitrary ISA extensions (without a sponsor, that is).  Given that the OPF ISA WG has to act entirely fairly i.e. in a non-discriminatory fashion towards all proposals, yet also take into account the huge burden of time and responsibility that results in perpetuity from any such inclusion, it is a reasonable balance.
 
-Note: the work that LibreSOC is doing is intended for the long term. Even if, by some mischance, LibreSOC was to evaporate the work that we are doing would still be available since what we do is open source.
+Yet at the same time, whilst being perfectly reasonable, we feel that our unique circumstances hsve not been anticipated.  We would therefore welcome some constructive feedback as to how we would go about submitting our work, and also how we can communicate effectively that we are in this for the long haul, and are committed to seeing it through.
+
+Note: the work that LibreSOC is doing is definitively intended for the long term.  Thanks to NLnet's "Works for the Public Good" remit, even if, by some mischance, LibreSOC was to evaporate the work that we are doing would still be available since what we do is entirely libre.
+
+At this point however it is important to provide some context as to why RED Semiconductor exists.  RED Semiconductor is being set up to realise LibreSOC designs and concepts in actual silicon.  It is NOT intended to REPLACE LibreSOC because to assign Copyright to a Corporation is prohibited by our relationship with NLnet (assigning to a Foundation however such as OPF is perfectly fine).
+
+Therefore whilst we in LibreSOC as individuals are the actual non-affiliated architects of the ISA Extensions, RED Semiconductor will not own the Copyright but will be in exactly the same boat as any other Corporation!
+
+The key person acting as the bridge between both world will be myself (Luke Legton), and I will ensure *and require* that RED Semiconductor provides adequate funds and resources for the long haul,