Lines Matching full:architecture

3 The POSIX architecture
14 The native simulator in combination with the POSIX architecture and the inf_clock SOC layer,
15 provide the foundation, architecture and SOC layers for a set of virtual test
22 Zephyr application, eliminating the need for architecture-specific
27    The POSIX architecture is not related and should not be confused with the
61    The POSIX architecture is known to **not** work on macOS due to
97 `Rationale for this port`_ and :ref:`Architecture<posix_arch_architecture>`
177 Currently, these are the most significant features which are not supported in this architecture:
188   :ref:`the architecture section's architecture layer paragraph <posix_arch_design_archl>`
240 This native port compiles your code directly for the host architecture
251 The drivers and HW models for this architecture will hide this from the
276 As instructions are translated to the host architecture, and the target CPU and
304 Architecture and design
310    :kconfig:option:`CONFIG_NATIVE_APPLICATION` based architecture.
311    It only describes the new native simulator based architecture used by targets built with the
336 with the :ref:`POSIX architecture<posix_arch_design_archl>` and the
400 The POSIX architecture is mainly responsible for two things:
402 * Set up the Zephyr build to produce an static library for the host architecture to be later
404 * Provide a thin adaptation between the API the Zephyr kernel expects from an architecture
412 This architecture provides the same interface to the Kernel as other
418 only used by the POSIX architecture to keep thread bookkeeping data.
420 When using this architecture, the code is compiled natively for the host system,
452 Note that the SOC/board split in this architecture is different than for other Zephyr targets.
453 This was done to enable very different real SOC simulations to share a common architecture and SOC