doc: tweaks for latexpdf build
Update missing captions on figures to remove remaining broken references during latexpdf building. Also, require doing a "make html" before doing a "make latexpdf" to build all the artifacts needed for running the latexpdf build. (We might change that later if needed.) Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
This commit is contained in:
parent
628bca5cad
commit
f596b6df13
|
@ -90,5 +90,5 @@ endif
|
|||
|
||||
# Catch-all target: route all unknown targets to Sphinx using the new
|
||||
# "make mode" option. $(OPTS) is meant as a shortcut for $(SPHINXOPTS).
|
||||
%: Makefile doxy
|
||||
%: Makefile
|
||||
@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(OPTS)
|
||||
|
|
|
@ -78,6 +78,8 @@ events in chronological order.
|
|||
:align: center
|
||||
:name: partBSPsetup
|
||||
|
||||
Event Order for Processor Set Up
|
||||
|
||||
Memory
|
||||
======
|
||||
|
||||
|
|
|
@ -43,6 +43,8 @@ Virtio-BLK BE Design
|
|||
:width: 900px
|
||||
:name: virtio-blk-be
|
||||
|
||||
Virtio-BLK BE Design
|
||||
|
||||
The virtio-blk BE device is implemented as a legacy virtio device. Its
|
||||
backend media could be a file or a partition. The virtio-blk device
|
||||
supports writeback and writethrough cache mode. In writeback mode,
|
||||
|
|
|
@ -140,6 +140,7 @@ details in this `Android keymaster functions document
|
|||
:width: 600px
|
||||
:name: keymaster-app
|
||||
|
||||
Keystore service and Keymaster HAL
|
||||
|
||||
As shown in :numref:`keymaster-app` above, the Keymaster HAL is a
|
||||
dynamically-loadable library used by the Keystore service to provide
|
||||
|
@ -191,6 +192,8 @@ forwards RPMB data frame to physical RPMB partition in eMMC.
|
|||
:width: 600px
|
||||
:name: trusty-ss-ta
|
||||
|
||||
Trusty Secure Storage Trusted App
|
||||
|
||||
As shown in :numref:`trusty-ss-ta` above, Trusty SS TA provides two different services
|
||||
simultaneously:
|
||||
|
||||
|
@ -227,6 +230,8 @@ open/creation/deletion/read/write operations.
|
|||
:width: 600px
|
||||
:name: trusty-ss-ta-storage
|
||||
|
||||
Trusty Secure Storage Trusted App Storage
|
||||
|
||||
Here is a simple example showing data signing:
|
||||
|
||||
#. An OEM Client App sends the message that needs signing to the OEM
|
||||
|
@ -268,6 +273,8 @@ secure monitor to schedule in/out Trusty secure world.
|
|||
:width: 600px
|
||||
:name: trusty-isolated
|
||||
|
||||
Trusty Secure World Isolated User VM
|
||||
|
||||
As shown in :numref:`trusty-isolated` above, the hypervisor creates an
|
||||
isolated secure world User VM to support a Trusty OS running in a User VM on
|
||||
ACRN.
|
||||
|
@ -282,6 +289,8 @@ Linux-based system (e.g. Android) runs.
|
|||
:width: 600px
|
||||
:name: trusty-lhs-rhs
|
||||
|
||||
Trusty Secure World Isolation Details
|
||||
|
||||
The secure world is configured by the hypervisor so it has read/write
|
||||
access to a non-secure world's memory space. But non-secure worlds do
|
||||
not have access to a secure world's memory. This is guaranteed by
|
||||
|
@ -325,6 +334,7 @@ high-level architecture.
|
|||
:width: 600px
|
||||
:name: trusty-rpmb
|
||||
|
||||
Virtualized Secure Storage Architecture
|
||||
|
||||
In :numref:`trusty-rpmb`, the rKey (RPMB AuthKey) is the physical RPMB
|
||||
authentication key used for data authenticated read/write access between
|
||||
|
|
Loading…
Reference in New Issue