index.md: ECLAIR: Add MISRA "product vs framework" intro
The idea is to convey that Trusted Firmware Open Source project does
not seek MISRA certification itself. Instead, the idea is to be
"MISRA ready", to facilitate MISRA compliance/certification for
downstream users.
Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
Change-Id: Ibda3a0767e61426d10ae8a684d6e47f9ee375229
diff --git a/docs/index.md b/docs/index.md
index d2a8dd3..64d9193 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -503,6 +503,22 @@
### MISRA analysis using ECLAIR tool
+[MISRA C](https://en.wikipedia.org/wiki/MISRA_C) is a well-known industry
+standard for ensuring system quality and safety. The Trusted Firmware project
+aspires to adhere to the MISRA guidelines as much as reasonably possible,
+with the help of its stakeholders and contributors. Note that to warrant
+a particular level of MISRA C compliance, a *specific product* must undergo
+MISRA C certification. An example of a "specific product" in the context
+of Trusted Firmware would be a particular version of Trusted Firmware configured
+for a particular target system, built with a specific toolchain, etc. The
+upstream Trusted Firmware project is not a specific product, but rather a
+framework / umbrella codebase with high number of configuration choices.
+The upstream project thus does not seek for MISRA C certification itself.
+Instead, the aim is to provide largely MISRA C compliant codebase, allow
+contributors to improve the level of compliance, and help downstream
+users / vendors to proceed with the formal MISRA C certification if they
+choose so.
+
Bugseng [ECLAIR](https://www.bugseng.com/eclair) is a proprietary advanced system
for in-depth MISRA analysis and reporting. One of its distinguishable
features is ability to work in "differential" mode - to report issues