Go to file
Håkon Alseth a88dc36f60 clang-format: add support for clang-format
Add .clang-format style from linux kernel to allow easier
style formatting for developers that do not use uncrustify.
You can call "clang-format -style=file -i my_src.c" within the repo
to in-place fix the style.

Signed-off-by: Håkon Alseth <haal@nordicsemi.no>
2018-11-19 09:31:44 -05:00
.github/ISSUE_TEMPLATE doc: Add issue templates 2018-11-10 15:06:04 -05:00
.known-issues doc: filter expected dup decl warnings 2018-11-05 23:40:26 -05:00
arch arch/arm: Avoid C++ comments inside C comments 2018-11-15 17:38:25 -05:00
boards ieee802154: cc2520: quark_se_c1000_devboard: Move all GPIOs to DTS 2018-11-16 14:02:00 -05:00
cmake cmake: Set PYTHON_EXECUTABLE env var with kconfig 2018-11-16 13:26:24 -05:00
doc doc: application: coccinelle: Add information about coccinelle list 2018-11-17 14:50:33 -05:00
drivers i2s: fix bad argument to k_mem_slab_free() 2018-11-16 18:26:03 -05:00
dts dts-binding: modem: wnc-14a2a: remove base_label to fix build errors 2018-11-17 00:50:15 -05:00
ext dts_fixups: Use DT_ prefix in all defined labels not related to Kconfig 2018-11-13 10:44:42 -06:00
include net: mqtt: Add TLS socket transport 2018-11-19 09:31:01 -05:00
kernel kernel: expose k_busy_wait() to user mode 2018-11-15 16:20:36 -05:00
lib lib/cmsis_rtos_v1: Use k_is_in_isr instead of _is_in_isr 2018-11-15 09:20:57 -05:00
misc misc/printk: Make the default char_out routine weak 2018-11-14 19:08:27 -05:00
samples samples: mqtt: Switch MQTT Publisher to new MQTT implementation 2018-11-19 09:31:01 -05:00
scripts kconfiglib/menuconfig/kconfig.py: Various improvements 2018-11-19 12:18:23 +01:00
soc dts-binding: modem: wnc-14a2a: remove base_label to fix build errors 2018-11-17 00:50:15 -05:00
subsys net: mqtt: Add TLS socket transport 2018-11-19 09:31:01 -05:00
tests tests: mqtt: Add test to verify publish reception 2018-11-19 09:31:01 -05:00
.checkpatch.conf checkpatch: define typedefsfile to deal with a few false positives 2017-10-09 10:43:05 -04:00
.clang-format clang-format: add support for clang-format 2018-11-19 09:31:44 -05:00
.codecov.yml ci: add .codecov.yml for codecov.io configuration 2018-01-03 13:12:03 -05:00
.gitattributes First commit 2015-04-10 16:44:37 -07:00
.gitignore gitignore: Ignore default bsimt_bt test output folder 2018-11-13 11:14:19 -05:00
.gitlint gitlint: use custom rule for line length violations 2018-02-07 15:28:36 -05:00
.mailmap mailmap: add entry for ruuddw 2018-07-05 09:57:23 -04:00
.shippable.yml ci: Run bsim_bt tests and collect coverage results 2018-11-13 11:14:19 -05:00
.uncrustify.cfg uncrustify: Add a rule to remove space inside function argument 2018-10-16 09:50:03 -04:00
CMakeLists.txt Revert "Build: Offsets lib as OBJECT not STATIC" 2018-11-17 22:28:33 -05:00
CODEOWNERS CODEOWNERS: Update list to add `scripts/coccinelle/` directory 2018-11-07 08:19:14 -05:00
CONTRIBUTING.rst doc: Fix a typo 2018-10-25 09:10:44 +01:00
Kconfig license: Replace Apache boilerplate with SPDX tag 2017-01-19 03:50:58 +00:00
Kconfig.zephyr kconfig: distribute misc/Kconfig option where they belong 2018-11-12 08:01:15 -05:00
LICENSE add top level Apache 2.0 license file 2016-02-05 20:24:37 -05:00
Makefile doc: document build target for PDF 2018-09-11 14:55:43 -04:00
README.rst docs: fixed documenation pointers 2018-09-12 12:03:18 -04:00
VERSION release: Post-release patch level update 2018-09-10 22:42:12 -04:00
version.h.in Introduce cmake-based rewrite of KBuild 2017-11-08 20:00:22 -05:00
zephyr-env.cmd scripts: fix west launcher for macOS 2018-09-26 00:33:45 +02:00
zephyr-env.sh env: Remove usage of -P in grep 2017-07-15 11:12:35 -07:00

README.rst

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/images/Zephyr-Project.png">
     </p>
   </a>

   <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

Getting Started
***************

To start developing Zephyr applications refer to the `Getting Started Guide`_
in the `Zephyr Documentation`_ pages.
A brief introduction to Zephyr can be found in the  `Zephyr Introduction`_
page.

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.

* **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
  http://docs.zephyrproject.org.  Additional documentation is maintained in
  the `Zephyr GitHub wiki`_.

* **Cross-reference**: Source code cross-reference for the Zephyr
  kernel and samples code is available at
  https://elixir.bootlin.com/zephyr/latest/source.

* **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 Development mailing list`_ is perhaps the most convenient
  way to track developer discussions and to ask your own support questions to
  the Zephyr project community.  There are also specific `Zephyr mailing list
  subgroups`_ for announcements, builds, marketing, and Technical
  Steering Committee notes, for example.
  You can read through the 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: http://docs.zephyrproject.org/latest/boards/boards.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Zephyr Introduction: http://docs.zephyrproject.org/latest/introduction/introducing_zephyr.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/getting_started/getting_started.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/contribute_guidelines.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Development mailing list: https://lists.zephyrproject.org/g/devel
.. _Zephyr mailing list subgroups: https://lists.zephyrproject.org/g/main/subgroups
.. _Sample and Demo Code Examples: http://docs.zephyrproject.org/latest/samples/samples.html
.. _Security Overview: http://docs.zephyrproject.org/latest/security/security-overview.html