Merge "doc: Set fconf as experimental feature" into integration
This commit is contained in:
commit
6e18633260
|
@ -73,6 +73,8 @@ Current features
|
||||||
to be configured at runtime if required by the platform. It also enables
|
to be configured at runtime if required by the platform. It also enables
|
||||||
loading of a hardware configuration (for example, a kernel device tree)
|
loading of a hardware configuration (for example, a kernel device tree)
|
||||||
as part of the FIP, to be passed through the firmware stages.
|
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
|
- Support for alternative boot flows, for example to support platforms where
|
||||||
the EL3 Runtime Software is loaded using other firmware or a separate
|
the EL3 Runtime Software is loaded using other firmware or a separate
|
||||||
|
|
|
@ -643,6 +643,7 @@ Common build options
|
||||||
- ``ARM_IO_IN_DTB``: This flag determines whether to use IO based on the
|
- ``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
|
firmware configuration framework. This will move the io_policies into a
|
||||||
configuration device tree, instead of static structure in the code base.
|
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.
|
- ``USE_ROMLIB``: This flag determines whether library at ROM will be used.
|
||||||
|
|
Loading…
Reference in New Issue