Find a file
David B. Kinder 8c708fd049 doc: fix misspellings and hyphen use
fixed error introduced in application.rst (v1.8) along with a general
spelling check pass including consistent spelling of "runtime" and
hyphenated words with "pre-"

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-09-20 15:33:43 -04:00
.known-issues net: doc: Add missing defgroups to network header files 2017-07-31 20:59:09 +03:00
arch kernel: allow up to 6 arguments for system calls 2017-09-20 09:18:59 -07:00
boards qemu_xtensa: enable stack sentinel 2017-09-12 22:31:18 -04:00
doc doc: fix misspellings and hyphen use 2017-09-20 15:33:43 -04:00
drivers drivers: i2c: remove usage of bitfield access for cfg 2017-09-20 10:16:14 -05:00
dts dts: stm32f4-pinctrl remove wrong pinmux configurations 2017-09-12 11:24:56 -04:00
ext ext: hal: nordic: Add missing nordic header file needed by nrf_power.h 2017-09-19 13:01:29 -05:00
include kernel: allow up to 6 arguments for system calls 2017-09-20 09:18:59 -07:00
kernel kernel: allow up to 6 arguments for system calls 2017-09-20 09:18:59 -07:00
lib lib: json: Silence warning about unused parameter 2017-09-07 05:49:17 -05:00
misc subsystem: cleanup misc and make cpp a subsystem 2017-07-06 09:13:46 -05:00
samples samples: net: sockets: Add HTTP GET example 2017-09-19 17:39:44 +03:00
scripts build: remove leftover qemu target 2017-09-19 10:54:31 -04:00
subsys net: dns: Do not resolve IPv6 address if IPv6 is disabled 2017-09-20 08:55:06 +03:00
tests net: dns: Do not resolve IPv6 address if IPv6 is disabled 2017-09-20 08:55:06 +03:00
.checkpatch.conf checkpatch: update checkpatch to warn about C99 type usage 2017-04-21 17:24:04 +00:00
.gitattributes First commit 2015-04-10 16:44:37 -07:00
.gitignore scripts: Convert gen_offset_header to Python 2017-07-24 11:20:04 -07:00
.gitlint scripts: allow "title" in commit titles 2017-09-15 16:36:49 -04:00
.mailmap mailmap: added axy (for Anas Nashif) 2016-12-21 13:49:59 +00:00
.shippable.yml ci: fix --only-failed mode of sanitycheck 2017-09-12 22:30:02 -04:00
CODEOWNERS cc3200: Remove TI cc3200 SOC and LaunchXL board support 2017-08-15 11:02:48 -05:00
CONTRIBUTING.rst doc: require license information for external code 2017-08-03 11:48:55 -04:00
Kbuild build: remove unused Kconfig variables 2017-08-03 07:19:29 -05:00
Kconfig license: Replace Apache boilerplate with SPDX tag 2017-01-19 03:50:58 +00:00
Kconfig.zephyr kconfig: move dts Kconfigs to dts/ 2017-08-03 07:19:29 -05:00
LICENSE add top level Apache 2.0 license file 2016-02-05 20:24:37 -05:00
Makefile scripts: move footprint scripts to footprint/ 2017-09-11 08:53:56 -07:00
Makefile.inc build: remove deprecated qemu/qemugdb targets 2017-08-03 11:48:55 -04:00
Makefile.test tests: introduce Makefile.test 2017-01-03 17:48:44 +00:00
README.rst doc: Add security doc mention in GitHub README 2017-08-25 14:22:56 -04:00
zephyr-env.sh env: Remove usage of -P in grep 2017-07-15 11:12:35 -07:00

Zephyr Project
##############

.. raw:: html

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>

The Zephyr Project is a scalable real-time operating system (RTOS) supporting
multiple hardware architectures, optimized for resource constrained devices,
and built with security in mind.

The Zephyr OS is based on a small-footprint kernel designed for use on
resource-constrained systems: from simple embedded environmental sensors and
LED wearables to sophisticated smart watches and IoT wireless gateways.

The Zephyr kernel supports multiple architectures, including ARM Cortex-M,
Intel x86, ARC, NIOS II, Tensilica Xtensa, and RISC V, and a large number of
`supported boards`_.

.. below included in doc/introduction/introduction.rst

.. start_include_here

Community Support
*****************

The Zephyr Project Developer Community includes developers from member
organizations and the general community all joining in the development of
software within the Zephyr Project. Members contribute and discuss ideas,
submit bugs and bug fixes, and provide training. They also help those in need
through the community's forums such as mailing lists and IRC channels. Anyone
can join the developer community and the community is always willing to help
its members and the User Community to get the most out of the Zephyr Project.

Welcome to the Zephyr community!

Resources
*********

Here's a quick summary of resources to find your way around the Zephyr Project
support systems:

* **Zephyr Project Website**: The https://zephyrproject.org website is the
  central source of information about the Zephyr Project. On this site, you'll
  find background and current information about the project as well as all the
  relevant links to project material.  For a quick start, refer to the
  `Zephyr Introduction`_ and `Getting Started Guide`_.

* **Releases**: Source code for Zephyr kernel releases are available at
  https://zephyrproject.org/downloads. On this page,
  you'll find release information, and links to download or clone source
  code from our GitHub repository.  You'll also find links for the Zephyr
  SDK, a moderated collection of tools and libraries used to develop your
  applications.

* **Source Code in GitHub**: Zephyr Project source code is maintained on a
  public GitHub repository at https://github.com/zephyrproject-rtos/zephyr.
  You'll find information about getting access to the repository and how to
  contribute to the project in this `Contribution Guide`_ document.

* **Samples Code**: In addition to the kernel source code, there are also
  many documented `Sample and Demo Code Examples`_ that can help show you
  how to use Zephyr services and subsystems.

* **Documentation**: Extensive Project technical documentation is developed
  along with the Zephyr kernel itself, and can be found at
  https://zephyrproject.org/doc.  Additional documentation is maintained in
  the `Zephyr GitHub wiki`_.

* **Issue Reporting and Tracking**: Requirements and Issue tracking is done in
  our JIRA system: https://jira.zephyrproject.org. You can browse through the
  reported issues and submit issues of your own.

* **Security-related Issue Reporting**: For security-related inquiries or
  reporting suspected security-related bugs in the Zephyr OS, please
  send email to vulnerabilities@zephyrproject.org.  We will assess and fix
  flaws according to our security policy outlined in the Zephyr Project
  `Security Overview`_.

* **Mailing List**: The `Zephyr Mailing Lists`_ are perhaps the most convenient
  way to track developer discussions and to ask your own support questions to
  the Zephyr project community.
  You can also read through message archives to follow
  past posts and discussions, a good thing to do to discover more about the
  Zephyr project.

* **IRC Chatting**: You can chat online with the Zephyr project developer
  community and other users in our IRC channel #zephyrproject on the
  freenode.net IRC server. You can use the http://webchat.freenode.net web
  client or use a client-side application such as pidgin.


.. _supported boards: https://www.zephyrproject.org/doc/boards/boards.html
.. _Zephyr Introduction: https://www.zephyrproject.org/doc/introduction/introducing_zephyr.html
.. _Getting Started Guide: https://www.zephyrproject.org/doc/getting_started/getting_started.html
.. _Contribution Guide: https://www.zephyrproject.org/doc/contribute/contribute_guidelines.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Mailing Lists: https://lists.zephyrproject.org/
.. _Sample and Demo Code Examples: https://www.zephyrproject.org/doc/samples/samples.html
.. _Security Overview: https://www.zephyrproject.org/doc/security/security-overview.html