Find a file
Bogdan Davidoaia 5dc68e3855 ieee802154: kw41z: adjust sequence timeouts
Sequence timeouts should be scaled to 16us, as TMR_PRESCALE was set
to 62.5kHz.

Also, radio warmup times and TX packet length need to be taken into
account.

Signed-off-by: Bogdan Davidoaia <bogdan.davidoaia@linaro.org>
2017-05-04 11:58:46 -04:00
.known-issues doc: update known issues with blutooth APIs 2017-04-30 11:40:26 -04:00
arch arch: sam3x: update Kconfig options after move to SAM SoC family tree 2017-05-03 13:51:37 -04:00
boards boards/galileo: Enable ethernet in the default configuration 2017-05-04 11:57:22 -04:00
doc doc: fix doc headings in security.rst 2017-05-01 23:14:38 -04:00
drivers ieee802154: kw41z: adjust sequence timeouts 2017-05-04 11:58:46 -04:00
dts arm: dts: ti_lm3s6965: Add device tree support for Stellaris UART 2017-04-28 15:26:40 -05:00
ext ext: Update Nordic MDK header files 2017-05-02 12:02:24 -05:00
include Bluetooth: Introduce buffer type parameter to bt_buf_get_rx 2017-05-04 16:38:34 +03:00
kernel test: benchmarking: Timing metrics for the kernel 2017-05-03 08:46:30 -04:00
lib lib: json: add JSON_OBJ_DESCR_PRIM 2017-05-03 13:52:57 -04:00
misc kconfig: Move debugging-related options from misc/ to subsys/debug/ 2017-04-28 23:41:16 +00:00
samples Bluetooth: Reshuffle Kconfig options 2017-05-04 11:27:04 +03:00
scripts ci: update path to theme repo 2017-05-03 15:36:03 -04:00
subsys Bluetooth: Consolidate flow control Kconfig 2017-05-04 18:09:31 +03:00
tests Bluetooth: Consolidate flow control Kconfig 2017-05-04 18:09:31 +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 doc: tweak .gitignore to allow doc theme dev 2017-02-23 13:20:04 +00:00
.gitlint scripts: add gitlint to check for validity of commit messages 2017-04-25 22:48:24 +00:00
.gitreview cc3220sf: Add support for the TI CC3220SF SoC 2017-04-28 15:06:41 -05:00
.mailmap mailmap: added axy (for Anas Nashif) 2016-12-21 13:49:59 +00:00
.shippable.yml CI: Fix the git commit range we pass on to gitlint 2017-05-04 11:25:35 -04:00
defaults.tc testcases: catch more fatal kernel error messages 2016-11-11 13:21:16 +00:00
Kbuild build: Add separate DTS target 2017-04-20 14:36:10 +00:00
Kconfig license: Replace Apache boilerplate with SPDX tag 2017-01-19 03:50:58 +00:00
Kconfig.zephyr license: Replace Apache boilerplate with SPDX tag 2017-01-19 03:50:58 +00:00
LICENSE add top level Apache 2.0 license file 2016-02-05 20:24:37 -05:00
MAINTAINERS MAINTAINERS: replace git pointer to github 2017-04-30 20:10:07 -04:00
Makefile build: build host-tools when prebuilts are enabled 2017-04-27 20:52:20 -04:00
Makefile.inc build: Add separate DTS target 2017-04-20 14:36:10 +00:00
Makefile.test tests: introduce Makefile.test 2017-01-03 17:48:44 +00:00
README.rst doc: remove :orphan: from README.rst 2017-04-29 15:33:36 -04:00
zephyr-env.sh zephyr-env.sh: only reset scripts_path on Windows 2017-03-31 15:42:31 -04:00

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Zephyr™ Project
###############

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 and RISC V, and a large number of
`supported boards`_.

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

Heres 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, youll
  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`_ wiki article.

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

* **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://github.com/zephyrproject-rtos/zephyr/wiki/Contribution-Guide
.. _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