FSP: Insufficient interface documentation
Open
- Dominant language
- C
- Stars
- 359
- Forks
- 142
- PR merge metrics
- No merged PRs in 30d
Description
Even with the integration guide it's impossible to understand what UPDs are actually doing.
If a firmware developer can't even properly understand what UPDs should be set, how should one use FSP in a secure manner?
Please improve the interface documentation of all FSP releases and explain in detail what an UPD is actually doing, which dependencies it has, if it works in RELEASE/DEBUG mode only ...
Contributor guide
Assessment
This issue has not been assessed yet.