Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
Go to file
ravishankar karkala Mallikarjunayya 5be0d4a706 tests/drivers/uart/uart_basic_api : Added build only tag
Testcase yaml requires some interactive inputs to be provided for
execution and hence fails on automation. Hence making it as build
only

Signed-off-by: ravishankar karkala Mallikarjunayya <ravix.shankar.km@intel.com>
2017-12-11 09:33:09 -05:00
.known-issues doc: add missing API content 2017-12-01 08:58:56 -05:00
arch ARM: stm32f0: fix syscfg mapping to fix EXTI config 2017-12-07 08:08:41 -06:00
boards doc: boards: v2m_beetle: fix conversion to cmake 2017-12-06 16:58:49 -06:00
cmake cmake: Show usage when an invalid board is given 2017-12-10 19:51:21 -05:00
doc doc: fix version parsing 2017-12-09 12:23:52 -05:00
drivers drivers: gpio: esp32: Check return value of pinmux_pin_input_enable() 2017-12-11 09:21:53 -05:00
dts yaml: fix properties syntax to 'mapping' instead of 'series' 2017-11-28 11:42:59 -06:00
ext ext: hal: altera: Add Altera HAL README file 2017-11-17 07:46:40 -05:00
include kernel: threads: remove thread groups 2017-12-09 08:48:51 -06:00
kernel kernel: remove reference to legacy_timer.c in build system 2017-12-09 08:48:51 -06:00
lib kbuild: Removed KBuild 2017-11-08 20:00:22 -05:00
misc cmake: add missing config for *.lst files 2017-12-04 10:18:51 -05:00
samples samples: Don't read board from cmake -DBOARD=x 2017-12-11 09:06:48 -05:00
scripts release: update sanitycheck footprint data 2017-12-08 08:09:55 -05:00
subsys net: if: Join solicited-node multicast addr for each unicast addr 2017-12-11 09:09:48 -05:00
tests tests/drivers/uart/uart_basic_api : Added build only tag 2017-12-11 09:33:09 -05:00
.checkpatch.conf checkpatch: define typedefsfile to deal with a few false positives 2017-10-09 10:43:05 -04:00
.gitattributes
.gitignore doc: report which warnings/errors are new 2017-11-13 17:45:42 -05:00
.gitlint scripts: allow "title" in commit titles 2017-09-15 16:36:49 -04:00
.mailmap
.shippable.yml ci: move doc.warnings up to be evaluated 2017-11-15 07:57:46 -05:00
CMakeLists.txt cmake: Fail with an error message when empty libraries exist 2017-12-10 19:51:54 -05:00
CODEOWNERS CODEOWNERS: add cmake owners 2017-11-08 20:00:22 -05:00
CONTRIBUTING.rst CONTRIBUTING.rst: add note about idling on IRC 2017-11-13 13:50:55 -08:00
Kconfig
Kconfig.zephyr
LICENSE
Makefile build: add top-level Makefile for docs 2017-11-08 20:00:22 -05:00
README.rst doc: update links to new zephyrproject.org site 2017-11-03 19:31:14 -04:00
VERSION release: Update PATCHLEVEL to 99 post 1.10.0 release 2017-12-08 14:31:07 -06:00
version.h.in Introduce cmake-based rewrite of KBuild 2017-11-08 20:00:22 -05:00
zephyr-env.sh

README.rst

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

.. raw:: html

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <img
   src="https://api.shippable.com/projects/58ffb2b8baa5e307002e1d79/badge?branch=master">


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/developers/#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
  the Github issues system: https://github.com/zephyrproject-rtos/zephyr/issues.
  You can browse through the reported issues and submit issues of your own.

* **Security-related Issue Reporting and Tracking**: 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`_.

  Security related issue tracking is done in JIRA.  The location of this JIRA
  is https://zephyrprojectsec.atlassian.net.

* **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