From c2c150e7c5bb9f56bd482a6ed98e28a7f1962edf Mon Sep 17 00:00:00 2001 From: Louis Mayencourt Date: Thu, 9 Apr 2020 16:32:20 +0100 Subject: [PATCH] doc: Set fconf as experimental feature Following the messages on the mailing list regarding the possible issue around reading DTB's information, we decided to flag the fconf feature as experimental. A uniform approach should be used to handle properties miss and DTB validation. Signed-off-by: Louis Mayencourt Change-Id: Ib3c86e81fb2e89452c593f68d825d3d8f505e1fb --- docs/about/features.rst | 2 ++ docs/getting_started/build-options.rst | 1 + 2 files changed, 3 insertions(+) diff --git a/docs/about/features.rst b/docs/about/features.rst index 58954725f..baec52b58 100644 --- a/docs/about/features.rst +++ b/docs/about/features.rst @@ -73,6 +73,8 @@ Current features to be configured at runtime if required by the platform. It also enables loading of a hardware configuration (for example, a kernel device tree) as part of the FIP, to be passed through the firmware stages. + This feature is now incorporated inside the firmware configuration framework + (fconf), which is still flagged as experimental. - Support for alternative boot flows, for example to support platforms where the EL3 Runtime Software is loaded using other firmware or a separate diff --git a/docs/getting_started/build-options.rst b/docs/getting_started/build-options.rst index 778b49c20..90fe83feb 100644 --- a/docs/getting_started/build-options.rst +++ b/docs/getting_started/build-options.rst @@ -643,6 +643,7 @@ Common build options - ``ARM_IO_IN_DTB``: This flag determines whether to use IO based on the firmware configuration framework. This will move the io_policies into a configuration device tree, instead of static structure in the code base. + This is currently an experimental feature. - ``USE_ROMLIB``: This flag determines whether library at ROM will be used. -- GitLab