mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2025-07-30 06:54:48 +00:00
doc: remove Android in introductory material
Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
This commit is contained in:
parent
74acdcf6e1
commit
83fa9b0d20
@ -6,10 +6,9 @@ Glossary of Terms
|
||||
.. glossary::
|
||||
:sorted:
|
||||
|
||||
AaaG
|
||||
LaaG
|
||||
WaaG
|
||||
Acronyms for Android, Linux, and Windows as a Guest VM. ACRN supports a
|
||||
Acronyms for Linux and Windows as a Guest VM. ACRN supports a
|
||||
variety of :term:`User VM` OS choices. Your choice depends on the
|
||||
needs of your application. For example, Windows is popular for
|
||||
Human-Machine Interface (HMI) applications in industrial applications,
|
||||
@ -172,7 +171,7 @@ Glossary of Terms
|
||||
User VM
|
||||
A :term:`VM` where user-defined environments and applications run. User VMs can
|
||||
run different OSes based on their needs, including for example, Ubuntu for
|
||||
an AI application, Android or Windows for a Human-Machine Interface, or a
|
||||
an AI application, Windows for a Human-Machine Interface, or a
|
||||
hard real-time control OS such as Zephyr, VxWorks, or RT-Linux for soft or
|
||||
hard real-time control. There are three types of ACRN User VMs: pre-launched,
|
||||
post-launched standard, and post-launched real-time. *(Historically, a
|
||||
|
@ -76,7 +76,7 @@ ACRN has these key capabilities and benefits:
|
||||
non-safety-critical domains coexisting on one SoC using Intel VT-backed
|
||||
isolation.
|
||||
* **Adaptable and Flexible**: ACRN has multi-OS support with efficient
|
||||
virtualization for VM OSs including Linux, Android, Zephyr, and Windows, as
|
||||
virtualization for VM OSs including Linux, Zephyr, and Windows, as
|
||||
needed for a variety of application use cases. ACRN scenario configurations
|
||||
support shared, partitioned, and hybrid VM models to support a variety of
|
||||
application use cases.
|
||||
@ -148,7 +148,7 @@ shared among the Service VM and User VMs. The Service VM is launched by the
|
||||
hypervisor after any pre-launched VMs are launched. The Service VM can access
|
||||
remaining hardware resources directly by running native drivers and provides
|
||||
device sharing services to the User VMs, through the Device Model. These
|
||||
post-launched User VMs can run one of many OSs including Ubuntu, Android,
|
||||
post-launched User VMs can run one of many OSs including Ubuntu or
|
||||
Windows, or a real-time OS such as Zephyr, VxWorks, or Xenomai. Because of its
|
||||
real-time capability, a real-time VM (RTVM) can be used for software
|
||||
programmable logic controller (PLC), inter-process communication (IPC), or
|
||||
|
Loading…
Reference in New Issue
Block a user