mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-16 02:31:56 +00:00
37340c7353
doc/kernel/overview/changes.rst contains information about changes from
kernel release 1.5 ("Version 1 Kernel") to the combined "Version 2
Kernel" and doc/porting/application.rst talked about how to change
applications using Version 1 interfaces to the Version 2 interface.
This information remains in the online tagged versions of the
documentation, but it's time to remove this from the current
documentation set. (Also removing example porting code.)
Fixes issue #1524
Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
28 lines
1.1 KiB
ReStructuredText
28 lines
1.1 KiB
ReStructuredText
.. _overview_v2:
|
|
|
|
Overview
|
|
########
|
|
|
|
The Zephyr kernel lies at the heart of every Zephyr application. It provides
|
|
a low footprint, high performance, multi-threaded execution environment
|
|
with a rich set of available features. The rest of the Zephyr ecosystem,
|
|
including device drivers, networking stack, and application-specific code,
|
|
uses the kernel's features to create a complete application.
|
|
|
|
The configurable nature of the kernel allows you to incorporate only those
|
|
features needed by your application, making it ideal for systems with limited
|
|
amounts of memory (as little as 2 KB!) or with simple multi-threading
|
|
requirements (such as a set of interrupt handlers and a single background task).
|
|
Examples of such systems include: embedded sensor hubs, environmental sensors,
|
|
simple LED wearable, and store inventory tags.
|
|
|
|
Applications requiring more memory (50 to 900 KB), multiple communication
|
|
devices (like WiFi and Bluetooth Low Energy), and complex multi-threading,
|
|
can also be developed using the Zephyr kernel. Examples of such systems
|
|
include: fitness wearables, smart watches, and IoT wireless gateways.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
source_tree.rst
|