Go to file
Andrzej Kaczmarek e9cece87bb Bluetooth: controller: Add definitions for AdvA and TargetA offsets
Both AdvA and TargetA have constant offset in extended header so it
makes sense to have dedicated definitions for those numbers.
AdvA is always placed at the beginning on extended header while TargetA
follows AdvA directly. There are no PDUs without AdvA and with only
TargetA.

Offsets of other fields depends on extended header contents and thus
are non constant.

Signed-off-by: Andrzej Kaczmarek <andrzej.kaczmarek@codecoup.pl>
2020-12-04 23:08:15 -05:00
.buildkite ci: double number of worker for Dec 2020 2020-12-03 14:32:16 -05:00
.github actions: manifest: Update to latest action revision 2020-11-27 20:12:46 +01:00
.known-issues doc: update known-issues for Sphinx==3.3.0 2020-11-03 15:27:37 +01:00
arch arch: aarch64: Use SP_EL0 instead of SP_ELx 2020-12-04 08:13:42 -05:00
boards boards: lpcxpresso55s69: enable TFM with MCUboot 2020-12-04 15:06:56 +02:00
cmake SPARC: add FPU support 2020-12-04 14:33:43 +02:00
doc doc: release 2.5: Announce the SPARC FPU support 2020-12-04 14:33:43 +02:00
drivers drivers: modem: sara-r4: Improve offload_sendmsg() support 2020-12-03 17:37:48 -05:00
dts dts: arm: st: f1: Add STM32f103xC 2020-12-03 10:54:38 -06:00
include arch: aarch64: Use SP_EL0 instead of SP_ELx 2020-12-04 08:13:42 -05:00
kernel kernel: sched: Change variable name in z_tick_sleep 2020-12-04 23:05:57 -05:00
lib lib/os/heap: minimize initial overallocation in the aligned case 2020-11-30 14:50:07 -05:00
misc
modules modules: tfm: BL2 default comment 2020-12-04 15:06:56 +02:00
samples net: syslog: Make sure CONFIG_LOG_IMMEDIATE is not set 2020-12-04 15:46:42 +02:00
scripts scripts: runners: bossac: Fix offset parameter 2020-12-03 10:50:23 -06:00
share cmake: Zephyr CMake package clean-up and minor fix 2020-08-19 12:52:33 -04:00
soc boards: set CPU_HAS_FPU on LEON3 soc and boards 2020-12-04 14:33:43 +02:00
subsys Bluetooth: controller: Add definitions for AdvA and TargetA offsets 2020-12-04 23:08:15 -05:00
tests Bluetooth: controller: removed node_rx for big create/terminate 2020-12-04 17:09:33 +01:00
.checkpatch.conf checkpatch: disable PREFER_SECTION 2020-10-30 15:51:46 +01:00
.clang-format clang-format: Update with latest FOR_EACH macro list 2020-05-02 11:23:13 -04:00
.codecov.yml
.editorconfig editorconfig: indent Kconfig files with tabs 2020-07-08 21:30:38 -04:00
.gitattributes gitattributes: Tell linguist to ignore test pattern files 2020-04-23 14:07:57 -04:00
.gitignore gitignore: exclude tests/drivers/build_all 2020-03-20 13:49:05 -05:00
.gitlint
.mailmap
.uncrustify.cfg
CMakeLists.txt cmake: using zephyr_get_compile_options_for_lang_as_string() 2020-12-03 09:23:07 -05:00
CODE_OF_CONDUCT.md
CODEOWNERS codeowners: Add myself for GSM modem files 2020-12-04 12:16:54 -06:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr cmake: ensure shields can be placed in other BOARD_ROOTs 2020-11-13 13:36:48 +01:00
LICENSE
MAINTAINERS.yml MAINTAINERS: Add myself to watchdog collaborators. 2020-12-02 07:52:39 -06:00
Makefile doc: provide a target to only generate doxygen 2020-04-11 08:40:54 -04:00
README.rst doc: Replace shippable badge with buildkite badge 2020-07-14 07:21:44 -05:00
VERSION release: Update patch level to 99 after the 2.4.0 release 2020-09-27 15:15:49 -05:00
version.h.in
west.yml west.yml: Update hal_nordic revision 2020-12-04 15:32:17 +02:00
zephyr-env.cmd
zephyr-env.sh zephyr_env.sh: Remove semicolons at ends of lines 2019-12-10 14:34:46 -08:00

.. 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>
   <a href="https://buildkite.com/zephyr/zephyr">
   <img
   src="https://badge.buildkite.com/f5bd0dc88306cee17c9b38e78d11bb74a6291e3f40e7d13f31.svg?branch=master"></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

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

Welcome to Zephyr! See the `Introduction to Zephyr`_ for a high-level overview,
and the documentation's `Getting Started Guide`_ to start developing.

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

Community support is provided via mailing lists and Slack; see the Resources
below for details.

.. _project-resources:

Resources
*********

Here's a quick summary of resources to help you find your way around:

* **Help**: `Asking for Help Tips`_
* **Documentation**: http://docs.zephyrproject.org (`Getting Started Guide`_)
* **Source Code**: https://github.com/zephyrproject-rtos/zephyr is the main
  repository; https://elixir.bootlin.com/zephyr/latest/source contains a
  searchable index
* **Releases**: https://github.com/zephyrproject-rtos/zephyr/releases
* **Samples and example code**: see `Sample and Demo Code Examples`_
* **Mailing Lists**: users@lists.zephyrproject.org and
  devel@lists.zephyrproject.org are the main user and developer mailing lists,
  respectively. You can join the developer's list and search its archives at
  `Zephyr Development mailing list`_. The other `Zephyr mailing list
  subgroups`_ have their own archives and sign-up pages.
* **Nightly CI Build Status**: https://lists.zephyrproject.org/g/builds
  The builds@lists.zephyrproject.org mailing list archives the CI
  (shippable) nightly build results.
* **Chat**: Zephyr's Slack workspace is https://zephyrproject.slack.com.  Use
  this `Slack Invite`_ to register.
* **Contributing**: see the `Contribution Guide`_
* **Wiki**: `Zephyr GitHub wiki`_
* **Issues**: https://github.com/zephyrproject-rtos/zephyr/issues
* **Security Issues**: Email vulnerabilities@zephyrproject.org to report
  security issues; also see our `Security`_ documentation. Security issues are
  tracked separately at https://zephyrprojectsec.atlassian.net.
* **Zephyr Project Website**: https://zephyrproject.org

.. _Slack Invite: https://tinyurl.com/y5glwylp
.. _supported boards: http://docs.zephyrproject.org/latest/boards/index.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Introduction to Zephyr: http://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/getting_started/index.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/index.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/index.html
.. _Security: http://docs.zephyrproject.org/latest/security/index.html
.. _Asking for Help Tips: https://docs.zephyrproject.org/latest/guides/getting-help.html