On 06.08.2021 23:41, Daniel P. Smith wrote: > My concerns/issues: > B1. The irony that XSM is unsupported but XSM + SILO is supported (for > Arm)
Just one remark here: Prior to SILO introduction (and to some perhaps ever afterwards), just like !XSM stood for "XSM dummy module", XSM stood for "XSM/Flask". There's pretty little core XSM code, and the reason for it to be considered unsupported was mainly the bad quality of Flask code (which no-one, not even the maintainer, ever cared to address, except maybe tiny aspects thereof). Which luckily ... > Deferrals and concessions in v3: > D1. Answering (A1) can be addressed later by reviewing, refreshing, and > expanding XSM documentation > D2. Will work with community to get XSM in a supported status to resolve > (B1) ... you aim to address. Until such point I think though that people better wouldn't be forced or talked into including unsupported code in their builds. (I say this without having looked at v3 yet; you may very well have taken care of this already.) Jan
